GNOME Bugzilla – Bug 706737
One item menu makes no sense
Last modified: 2021-07-05 14:19:43 UTC
A (sub) menu with only one item in it looks odd. If there is just one item you could as well just show it instead of the indirection through the menu. This happens when you enable logout and have just one user. I suggest just showing "Logout" instead of the "Name > Logout" hierarchy.
did we want to do this for 3.10, still ? a patch would be needed soon
Do we have any design input on this? As far as I can see, doing it generally would result in the battery status being replaced by "Power Settings" ...
(In reply to comment #2) > Do we have any design input on this? Yes: Aug 26 17:26:57 <aday> submenus with only one item are a bit crap, indeed Aug 26 17:27:12 <aday> however, it is consistent with the other items at least Aug 26 17:27:35 * elad hat die Verbindung getrennt (Read error: 131 (Connection reset by peer)) Aug 26 17:27:45 <aday> i wouldn't object to this if it's not too much of a burden to maintain Aug 26 17:28:04 <drago01> ok Aug 26 17:28:21 <aday> drago01, this would only be in the single user case, right? Aug 26 17:28:32 <aday> ie. if you have logout enabled and multiple users, you would get the submenu Aug 26 17:28:36 <drago01> aday: yes
(In reply to comment #2) > Do we have any design input on this? As far as I can see, doing it generally > would result in the battery status being replaced by "Power Settings" ... Yeah the power submenu sucks. We can't really get rid of the submenu in that case though - it would be too disruptive to that section of the system menu. The only option is to find something else to add to that submenu (we've wanted a "What's using power?" link since forever). I don't think this stops us from fixing the user name issue here though. (Bug 709167 is also relevant.)
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/ Thank you for your understanding and your help.