After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 301827 - Keyboard equivalents in menus should be left-aligned by non-modifier
Keyboard equivalents in menus should be left-aligned by non-modifier
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: GtkMenu
unspecified
Other Linux
: Normal enhancement
: Small feature
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2005-04-24 20:31 UTC by Matthew Paul Thomas (mpt)
Modified: 2018-04-15 00:14 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10


Description Matthew Paul Thomas (mpt) 2005-04-24 20:31:46 UTC 
Distribution/Version: Ubuntu 5.04

Steps to reproduce:
1.  Open a menu where many adjacent items have keyboard equivalents, especially
    one where the keyboard equivalents are of very different widths. One good
    example of this is Epiphany's "Go" menu.
2.  Look at the layout of the keyboard equivalents.

What you should see:
        Alt+Left
        Alt+Right
        Alt+Up
    -------------
        Alt+Home
       Ctrl+H
    -------------
       Ctrl+L

What you actually see:
         Alt+Left
        Alt+Right
           Alt+Up
    -------------
         Alt+Home
           Ctrl+H
    -------------
           Ctrl+L

The non-modifier keys (e.g. Left, Right, Up, Home, H, L) should be left-aligned
with each other. Otherwise the staggered "+" characters look messy.
Comment 1 Tim Janik 2006-09-22 12:15:38 UTC 
can you provie _any_ reason for wanting a different alginment?
Comment 2 Matthew Paul Thomas (mpt) 2006-09-23 21:01:48 UTC 
I provided the reason in the original report: "Otherwise the staggered '+' characters look messy." (Where several consecutive items use the same modifier, aligning them would also make the key combos faster to scan.)
Comment 3 pablodalama 2006-10-13 02:55:30 UTC 
*** Bug 361820 has been marked as a duplicate of this bug. ***
Comment 4 Matthias Clasen 2018-02-10 05:01:14 UTC 
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
Comment 5 Matthias Clasen 2018-04-15 00:14:25 UTC 
As announced a while ago, we are migrating to gitlab, and bugs that haven't seen activity in the last year or so will be not be migrated, but closed out in bugzilla.

If this bug is still relevant to you, you can open a new issue describing the symptoms and how to reproduce it with gtk 3.22.x or master in gitlab:

https://gitlab.gnome.org/GNOME/gtk/issues/new