Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 371900

Summary:	[Chrome]Hovering on files introduces empty black span on tool bar in replace page.
Product:	[ECD] Orion	Reporter:	libing wang <libingw>
Component:	Client	Assignee:	Project Inbox <orion.client-inbox>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	ken_walker, mamacdon, susan
Version:	0.4
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description libing wang

2012-02-17 11:00:39 EST

If you search something and go to replace preview, you will find there is a black strip at the bottom of the tool bar when you hover on files or use up/down arrow key to navigate.
This does not happen when you hide the compare view.
I did some investigation, this "black strip" was introduced when dojo.toggleClass is called. Strange. 
One possible reason may be that in the compare mode the right pane is nested with border containers while in the non-compare mode the right pane is what ever comes from the html.
But I am sure the issue was not there 2 or 3 days ago. Must be related to some recent changes.

Comment 1 libing wang

2012-02-17 11:04:10 EST

Susan, any insight on this?

Comment 2 Susan McCourt

2012-02-17 11:20:55 EST

what class is being toggled?  perhaps the CSS itself changed?

Comment 3 libing wang

2012-02-17 11:33:17 EST

(In reply to comment #2)
> what class is being toggled?  perhaps the CSS itself changed?

"treeIterationCursor" for navigating and "fileNameCheckedRow" for hovering.
But my gut feeling is that it is not due to the CSS class itself because the non-compare mode does not reproduce the issue. Must be some thing deep inside the nested border container. Just a guess though.

Comment 4 Ken Walker

2012-02-17 12:01:10 EST

I don't see anything weird on Safari

Comment 5 libing wang

2012-02-17 12:08:07 EST

(In reply to comment #4)
> I don't see anything weird on Safari

Talked to Susan. She did not reproduce it in Chrome 16.
I am using Chrome 18. Might be upgraded from 16 recently. That is why I did not see it several days ago.
There is another Bug 371492 regarding Chrome 18.

Comment 6 libing wang

2012-02-17 12:12:08 EST

Confirmed that my fire fox did not reproduce it.
Change the subject key word as [Chrome] so later on we can look at all related bugs.

Comment 7 John Arthorne

2015-05-05 14:37:14 EDT

Closing as part of a mass clean up of inactive bugs. Please reopen if this problem still occurs or is relevant to you. For more details see:

https://dev.eclipse.org/mhonarc/lists/orion-dev/msg03444.html