Moving diagonally from narrow menu title often opens adjacent menu
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
One Hundred Papercuts |
Triaged
|
Low
|
Unassigned | ||
Unity |
Fix Released
|
Medium
|
Andrea Azzarone | ||
gtk+2.0 (Ubuntu) |
Triaged
|
Low
|
Unassigned | ||
gtk+3.0 (Ubuntu) |
Triaged
|
Low
|
Unassigned | ||
unity (Ubuntu) |
Fix Released
|
Medium
|
Andrea Azzarone |
Bug Description
gtk 2.22, Ubuntu 10.10
1. Click on the volume control to open the sound menu.
2. Move the pointer diagonally to click on the maximum volume button.
<https:/
What often happens: The sound menu closes, and the menu next to it opens.
Screencast: <https:/
Example in an informal usability test: <https:/
What should happen: The sound menu stays open.
One solution would be to make the volume slider vertical. But this would not work for other menus (like the Bluetooth menu), and would look awkward with other items in the menu.
Another solution would be to use a timer for closing the current menu and opening a new one. This is what Windows does for submenus. But it has the drawback of slowing down browsing, which would be worse for top-level menus than for submenus.
GTK already has a more sophisticated solution for submenus, similar to Mac OS: a triangle based on the corners of the submenu and its parent item, in which there is a much longer delay for closing the submenu and changing the menu selection. <http://
Discussion of the invisible triangle for submenus in GTK:
<http://
However, this feature in Gtk+ has been broken since July 2013. <https:/
More information: <http://
Related branches
- Marco Trevisan (Treviño): Approve
- PS Jenkins bot (community): Needs Fixing (continuous-integration)
-
Diff: 152 lines (+69/-9)2 files modifiedpanel/PanelView.cpp (+64/-8)
panel/PanelView.h (+5/-1)
description: | updated |
summary: |
- Auto-expanding AppIndicator menus makes navigating to menu items harder + Moving diagonally from narrow menu title often opens adjacent menu |
Changed in gtk+3.0 (Ubuntu): | |
status: | New → Confirmed |
Changed in unity (Ubuntu): | |
status: | New → Triaged |
Changed in unity (Ubuntu): | |
importance: | Undecided → Medium |
Changed in hundredpapercuts: | |
milestone: | nt7-potpourri → raring-gtk |
description: | updated |
Changed in hundredpapercuts: | |
assignee: | Papercuts Ninjas (papercuts-ninja) → nobody |
description: | updated |
tags: | added: 16.04-hit-list |
Changed in unity: | |
status: | Triaged → In Progress |
Changed in unity (Ubuntu): | |
status: | Triaged → In Progress |
assignee: | nobody → Andrea Azzarone (azzar1) |
Changed in unity: | |
assignee: | nobody → Andrea Azzarone (azzar1) |
milestone: | none → 7.3.3 |
tags: | added: rls-w-incoming |
Changed in unity: | |
status: | In Progress → Fix Committed |
Changed in unity: | |
status: | Fix Committed → Fix Released |
tags: |
added: rls-x-incoming removed: rls-w-incoming |
tags: | removed: rls-x-incoming |
Thank you for helping with making Ubuntu better by reporting this bug. We've briefly discussed this issue on IRC and decided that this issue deserves some more attention. I'm marking this bug as Triaged and am opening an task in the upstream project so we can keep track of it there as well.