| Summary: | Clicking on a toolbar no longer activates the view | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Paul Webster <pwebster> |
| Component: | UI | Assignee: | Platform-UI-Inbox <Platform-UI-Inbox> |
| Status: | CLOSED DUPLICATE | QA Contact: | Eric Moffatt <emoffatt> |
| Severity: | major | ||
| Priority: | P3 | CC: | carolynmacleod4, daniel_megert, emoffatt, markus.kell.r |
| Version: | 4.3 | ||
| Target Milestone: | 4.3 M7 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| URL: | http://download.eclipse.org/eclipse/downloads/drops4/I20130313-2000/testresults/html/org.eclipse.e4.ui.tests_linux.gtk.x86_6.0.html | ||
| Whiteboard: | |||
|
Description
Paul Webster
Temporarily disabled the test. http://git.eclipse.org/c/platform/eclipse.platform.ui.git/commit/?id=3af2efd59dc1be16044fe2dcbc192dbc0013623d PW Very easy to reproduce: Have a Package Explorer open with something expanded in it Activate a part in another stack Click one of the buttons on the PE's toolbar...it doesn't activate This is the result of the last fix for Bug 376011. This involved removing the SWT.Activate listener for the CTF in order to get the Tab traversal to be symmetric. The largest negative effect of this defect is that if the operation chosen is to open a dialog it won't (many other operations work OK). I can work around this one by explicitly activating the part in the 'showMenu' handlers since we construct them in the StackRenderer. Fixing this for the Toolbar is somewhat more problematic in that we don't (directly) own the code that manages the toolbar items... Paul and I have decided to live with this for M6 and start (immediately) to look for a proper solution which maintains the symmetry of the tabbing behavior but also activates the part whose TB was clicked. Car is looking into whether we can augment the SWT.Activate event with enough extra info to be able to determine whether the event occurred from a mouse click (where we want to activate the part) vs a KB event (where we don't). We're tracking the fix for this as part of bug 376011 so I'll mark this one as a dup of that one (the original 'fix' for that defect introduced this regression...). *** This bug has been marked as a duplicate of bug 376011 *** Verified in I20130409-0900. |