Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 479177 - Percentages disappear when item is clicked (NOTE: Happens on IE, not Chrome)
Summary: Percentages disappear when item is clicked (NOTE: Happens on IE, not Chrome)
Status: RESOLVED FIXED
Alias: None
Product: Orion
Classification: ECD
Component: JS Tools (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 471947
  Show dependency tree
 
Reported: 2015-10-06 15:24 EDT by Steve Northover CLA
Modified: 2015-10-27 15:39 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Steve Northover CLA 2015-10-06 15:24:34 EDT
1) In minesweeper-object (I can provide the project if necessary)
2) Open file 'board.js'
3) Click on the function isSwept()
4) Tools->References->Project
5) In the search dialog that pops up, click on 'if (self.isSwept () || self.isExploded ())' (DO NOT CLICK ON A PERCANTAGE)
6) BUG: the percentage disappears

I understand that the UI is not finalize, it's IE etc. etc. but I thought I'd report the bug.  It does not happen on Chrome (no idea about FF)
Comment 1 Michael Rennie CLA 2015-10-07 14:26:47 EDT
I think this will be addressed with some pending changes we having coming where we will no longer show the percentages, instead we will show the matches grouped like:

Exact Matches
Possible Matches
Unrelated Matches

This grouping will apply to what was the flat list layout.

For the other grouping (by location), we might use the same grouping above, but inside the location grouping. That way we can avoid cluttering the UI with piles of percentages.

For example we would could have:

Function Calls
   Exact Matches
   Possible Matches
   Unrelated Matches
JSDoc Comments
   Exact Matches
   Possible Matches
   Unrelated Matches

etc.
Comment 2 Michael Rennie CLA 2015-10-07 14:28:34 EDT
Each match would also look a bit different like:

(filename: line#) matchText

or

matchText (filename: line#)
Comment 3 Steve Northover CLA 2015-10-07 17:24:30 EDT
Did you type the comment in the wrong bug?  This is a straight up "the UI fails on IE but not on Chrome" thing that might just go away when we change the UI.  Is that what you were getting at?
Comment 4 Michael Rennie CLA 2015-10-08 10:14:57 EDT
(In reply to Steve Northover from comment #3)
> Did you type the comment in the wrong bug?  This is a straight up "the UI
> fails on IE but not on Chrome" thing that might just go away when we change
> the UI.  Is that what you were getting at?

That is exactly what I was getting at.
Comment 5 Steve Northover CLA 2015-10-27 15:39:40 EDT
This is not working.