Community
Participate
Working Groups
- 4.2M7 test build I20120429-1800 (with the new ToolBar implementation) - works fine with the old ToolBar implementation - open a .java file in the eclipse editor - make a change in the editor so that the Save toolbar button at the top becomes enabled - tab to this button and press Space to invoke it - the change is saved and the Save toolbar button is disabled - pressing tab repeatedly will reveal that focus is now nowhere, which isn't good
Actually this is an accessibility problem because once focus has disappeared then other keys like Ctrl+F6 which can be used to re-locate focus become unusable.
Hi Grant, I tested this with a M7 build (I20120427-0800) which doesn't contain my new Toolbar changes and I'm still able to reproduce the exact same behavior as described above. I even tested with a few earlier milestone builds of 4.2 to confirm and I see the same behavior there too. It worked fine for me with Indigo SR2. So, IMO this bug is not caused by the new Toolbar implementation. I'm wondering if it needs to be fixed in UI or somewhere else but I'm not very sure. Do you think we can move it to UI for primary investigation?
It's up to us to ensure that focus goes somewhere reasonable in a case like this. I believe the swt framework takes care of doing this in the case of a focused Control becoming disabled, but ToolBar/ToolItem may need some additional lines to consider this case since ToolItems are not Controls.
Hi Grant, Do we have any workaround for this. We also face the same issue with eclipse 4.2 .
Moving to Arun. I've confirmed the behaviour change by comparing the comment 0 steps between Eclipse 3.7.2 and 4.3.
I cannot tab to the save button in I20181206-0815. Is this still relevant?
I cannot reproduce this issue with SWT from master, GTK3.24, and Fedora 29.