In a number of new toolbar drop downs like the new color picker, line spacing, and insert table, there are underlined letters that should pick a particular button if you type the underscored letter, but unfortunately this does not work. This issue can only be found in 4.4 and master. We do have drop downs with similar underlined letters that do work when pressed like new, paste special, and insert field. Version: 4.4.0.0.alpha2+ Build ID: 797db638870f5c6192e72c0b4669b471788e16ea TinderBox: Linux-rpm_deb-x86@45-TDF, Branch:master, Time: 2014-11-20_03:50:17
I confirm it under Win8.1x64 using 4.5.0.0.alpha0+ Build ID: 84a6d8eeaab540e5b2ea3baffd919903dff8c247 TinderBox: Win-x86@39, Branch:master, Time: 2014-11-22_23:41:04 Locale: it_IT if this bug is already present in 4.4.x as you reported the version number has to be changed accordingly so I'm editing that field
Kendy stated in a previous design meeting that the underlines should be removed to solve this issue, as they werent there previously in the insert table or line spacing drop downs.
Actually, it is a UX consistency and accessibility issue. The hard coded menus have tilde "~", the .UI based menus and dialogs use underscore "_" to assign the key assigned as an accelerator--and that need to be announced in assistive technology interfaces. So, the underline could be removed--especially if there is no action actually assigned to the accelerator, but that would not result in the UI/UX that is needed. Consistent accelerators on menus and for button dialogs are fundamental to providing accessibility support. Ideally every menu item should have an accelerator assigned, and to extent possible every button widget should have an accelerator so that the UI can be used efficiently without use of a mouse or with a dependency on a visual display. Some would be global, some would be contextual to the dialog or panel that is active. Either way there are a lot within the UI that still need to be implemented.
(This is an automated message.) Setting priority to highest as this is a MAB. This is part of an effort to make the importance of MAB reflected in priority too.
This is a technical issue that requires no UX feedback. Please take care of not spamming the ux-advise list with bugs like this one.
Should this even be a MAB? Probably not, it is just that accelerators for some newly implemented menu items are broken in the UI (actually just not fully implemented--yet) question now is how to fix in a timely fashion. Design/UX says either remove the offending accelerator assignments ("_"'s in the UI config files), or identify appropriate .uno command to associate and do it. Or some mix there of.
I retested under Win8.1 x64 and seems it works in LibO 4.4.3.2 and 5.1.0.0 alpha I set status to WORKSFORME feel free to revert it if you think I'mwrong
I retested under Win8.1 x64 and seems it works in LibO 4.4.3.2 and 5.1.0.0 alpha I set status to WORKSFORME feel free to revert it if you think I'm wrong
Issue is still there. Version: 5.1.0.0.alpha1+ Build ID: 902255645328efde34ddf62227c8278e8dd61ff0 TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2015-07-30_05:23:12 Locale: en-US (en_US.UTF-8)
I confirm it is FIXED under Windows (retested with LibO 4.4.5.1 and recent 5.1.0.0 alpha daily build). so I change the hardware to Linux according to previous comment
Migrating Whiteboard tags to Keywords: (a11y -> accessibility)
Looks to me as a duplicate of Bug 84699. *** This bug has been marked as a duplicate of bug 84699 ***