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

Bug 346737

Summary:	Focus goes crazy with conflicting breadcrumb toggling command
Product:	[Eclipse Project] Platform	Reporter:	Remy Suen <remy.suen>
Component:	UI	Assignee:	Platform UI Triaged <platform-ui-triaged>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	gheorghe, markus.kell.r, pwebster, remy.suen
Version:	4.1
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description Remy Suen

2011-05-20 12:54:32 EDT

1. Open a Java editor.
2. Disable the breadcrumbs if they're on.
3. Window > Preferences > General > Keys
4. Find 'Show In Breadcrumb' for 'Editing Java Source'. Select this entry.
5. Click 'Copy Command'.
6. Assign this new command an 'Alt+Shift+B' binding, just like the original. You will now get a conflict.
7. Click 'OK'.
8. Hit Alt+Shift+B. The window will now flash constantly it seems to go in some kind of a focus loop. Clicking and hitting the 'Esc' key repeatedly will (eventually) get you out of this state.

Comment 1 Remy Suen

2011-05-27 14:13:59 EDT

This problem is not restricted to the Java editor's breadcrumbs feature. If I copy the 'Add Javadoc Comment' and give them both the Alt+Shift+J keybinding, the focus loop will occur.

Comment 2 Remy Suen

2011-05-30 09:42:29 EDT

The display filter is being notified multiple times even if I change the code for it to not do anything.

org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher$KeyDownFilter.handleEvent(KeyBindingDispatcher.java:83)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
	at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1262)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1052)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1077)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1062)
	at org.eclipse.swt.widgets.Control.traverse(Control.java:4033)
	at org.eclipse.swt.widgets.Control.translateMnemonic(Control.java:3875)
	at org.eclipse.swt.widgets.Composite.translateMnemonic(Composite.java:1178)
	at org.eclipse.swt.widgets.Composite.translateMnemonic(Composite.java:1183)
	at org.eclipse.swt.widgets.Composite.translateMnemonic(Composite.java:1183)
	at org.eclipse.swt.widgets.Composite.translateMnemonic(Composite.java:1183)
	at org.eclipse.swt.widgets.Composite.translateMnemonic(Composite.java:1183)
	at org.eclipse.swt.widgets.Control.translateMnemonic(Control.java:3893)
	at org.eclipse.swt.widgets.Display.translateMnemonic(Display.java:4770)
	at org.eclipse.swt.widgets.Display.filterMessage(Display.java:1276)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3748)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:944)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)

Comment 3 Remy Suen

2011-05-30 13:47:35 EDT

This bug happens on Eclipse 3.x also. As such, I don't really feel inclined to try to fix or workaround this problem.

Comments?

Comment 4 Remy Suen

2011-05-30 17:06:19 EDT

On the Mac, not printing any traverse events is expected because...that concept apparently isn't on a Mac.

On Linux, if you hit Alt+J, you will get the traverse events. It seems the Alt+Shift+J capitalization of the 'J' cancels it out. It's a small discrepancy but doesn't appear to be something to cry home about.

Comment 5 Remy Suen

2011-08-16 10:37:26 EDT

Removing 4.1.1 target as this bug happens in 3.x also.

Comment 6 Remy Suen

2011-10-07 10:40:07 EDT

*** Bug 360226 has been marked as a duplicate of this bug. ***

Comment 7 Lars Vogel

2019-11-14 03:46:36 EST

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.