Community
Participate
Working Groups
Created attachment 288326 [details] mnemonic key_English screenshot Build id: I20220323-1001 Problem: In the same panel, some strings have mnemonic keys, while some doesn't. JPN tester asked to have all the strings with mnemonic keys. This may refer to all the tabs for 'Custom clean ups' dialog. Steps to reproduce: Double click in desktop to open Eclipse client. Click Launch with default workspace Click Create a Java project if you don't have a project opened Input project name(e.g 'Demo') and click Finish directly Click 'Create' button if the dialog appears. Click Source-> Clean Up...in the top menu Click Use custom profile radio first -> then click Configure...button Click Unnecessary Code tab
Created attachment 288327 [details] screenshot from JPN tester
NL mnemonic keys are defined according to En ones. Dev team will evaluate the English mnemonic key fixes.
Few mnemonics will be repeated, as there are more than 26 words/lines needing mnemonics on the same page.
New Gerrit change created: https://git.eclipse.org/r/c/jdt/eclipse.jdt.ui/+/192386
New Gerrit change created: https://git.eclipse.org/r/c/jdt/eclipse.jdt.ui/+/192136
New Gerrit change created: https://git.eclipse.org/r/c/jdt/eclipse.jdt.ui/+/192388
(In reply to Kathy from comment #2) > NL mnemonic keys are defined according to En ones. Dev team will evaluate > the English mnemonic key fixes. After working on this closely we realized: 1. Problem existed with 4.19 also 2. Tried adding the mnemonics but we have around 35 words where we need mnemonic and we cannot do that with current tab structure. Adding duplicate mnemonics does not help for check boxes ans they don't move to next value, they check/uncheck on the repeated selction. 3. We plan to re organize this UI so that we don't have so many things in the same pane but this needs lot of thinking and cannot be done in hurry. We propose this to defer to the next release.
To be fixed in 4.24.
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. -- The automated Eclipse Genie.
