https://bugs.kde.org/show_bug.cgi?id=491519
Nate Graham <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |NOT A BUG --- Comment #3 from Nate Graham <[email protected]> --- You aren't the first person to think of some kind of global "how I want my menus shown" setting, but the challenge is that today every app supports different things: - No menus at all (many simple GNOME apps and some simple mobile-focused KDE apps) - Only a hardcoded hamburger menu button (many GNOME apps) - Only a conditionally-visible hamburger menu button (some small KDE apps) - An in-window menubar that is not compatible with the global menu feature (all Electron apps) - An in-window menubar that is not compatible with the global menu feature, and a hardcoded hamburger menu (Firefox) - An in-window menu that is compatible with the global menu feature (most QtWidgets-based KDE apps) - An in-window menu that is compatible with the global menu feature, plus a hardcoded hamburger menu button (Chromium/Chrome) - An in-window menu that is compatible with the global menu feature, plus a conditionally-visible hamburger menu button (some newer or more recently modernized QtWidgets-based KDE apps) In such a heterogenous, nonstandardized environment, it's hard to make promises because almost everything will be a lie, or need enough qualifiers documented that the feature feels super buggy and broken. As such, I think we have to shelve the idea for now. So let's re-focus on any small, actionable menu-related bugs you may be encountering. Can you open new bug reports for those — one per affected app. Thanks! -- You are receiving this mail because: You are watching all bug changes.
