GNOME Bugzilla – Bug 99297
GNOME Menu should post like a menu via F10
Last modified: 2015-03-24 13:00:56 UTC
GNOME menu; looks like a menu, smells like a menu, acts like a menu *except*, wait; F10 doesn't post it, it takes focus via tab and spacebar activates it? Since it's usually a single instance on a panel with no other menus, seems it would be better for users if it obeyed menu keynav semantics rather than button. Especially since once you activate it via spacebar, it clearly looks and behaves like a menu (Esc to unpost, etc.)
This bug should be logged as a gtk+ bug, not a GOK bug; there is really nothing GOK can do about it, only gtk+ can fix this problem.
arrgh, disregard previous comment, mozilla/bugzilla are doing something horrible to me at the moment.
huh? But you were recently arguing that the menubar should receive focus and activate on spacebar .... ?
yes, that's no contradiction (saying that menubar should activate on focus/spacebar). but that's not this bug;this bug is "if it smells like a menu, it should act like a menu" i.e. we call it a menu, it clearly results in menus being posted, thus it should adhere to common keybindings. As long as we use F10 to post menus generally (which does not, by the way, preclude their being in the focus chain), we need to make this keybinding available consistently. The foot menu is ATM the only popup/dropdown (i.e. non-context-menu) menu that doesn't conform.
F10 cycles through menubars in the current window selecting the first item in the menubar. The current proposal for fixing bug 89336 is that F10 would not cause the submenu to be posted.
Padraig, how does your comment above impinge on this bug? Other than the notion that failing to automatically-post the submenu would probably be a plus for the foot menu...
My reading of the description of the bug is that a Gnome menu should be posted via F10 because F10 is used to post menus. I am questioning whether this is true. It looks to me that you are asking that the Gnome Foot be reimplemented as a menubar instead of as a button.
I think the GNOME foot should post like a menu. Whether that's accomplished by reimplementing it as a menubar is not something I have an opinion about. But since it's clearly a menu (conceptually), and a special-case singleton at that, I believe it would be reasonable to do this either via making it a menubar or by tweaking gnome-panel to activate it on receipt of F10, i.e. special case gnome-panel to include the GNOME foot in its menu list.
Updating status_whiteboard field to reflect A11Y team's assessment of accessibility impact.
Something deep within me keeps saying that F10 shouldn't really have a place on the panels at all, and that you should have to navigate to menus the same way you navigate to anything else on a panel :) But until I come up with a good rationale for that, I agree it would probably be good if the Gnome menu was included in the F10 keynav chain for a panel.
(And likewise, it would be great if the menu applet / window list applet were included in the tab chain for a panel, as well as popping up on F10).
Apologies for spam... marking as GNOMEVER2.3 so it appears on the official GNOME bug list :)
Apologies for spam-- ensuring Sun a11y team are cc'ed on all current a11y bugs. Filter on "SUN A11Y SPAM" to ignore.
FWIW it would be convenient if GOK could recognize the launcher as SPI_ROLE_MENU_ITEM. Is there any activity on this bug?
We'll try to fix this for 2.12. I'll probably need some explanations, though :-)
Mass changing: milestone 2.12.x => milestone 2.14.x
Apologies for spam... ensuring Sun a11y folks are cc'ed on all current accessibility bugs.
Closing this. No activity for 7+ years, and I don't see gnome-panel going through any more design iterations.