https://bugs.kde.org/show_bug.cgi?id=501871
--- Comment #9 from Felix Ernst <felixer...@kde.org> --- (In reply to Nate Graham from comment #7) > I'm surprised by that, because we already hide the hamburger menu when > there's an in-window menubar; I don't seem why it should be different if > instead there's a global menu. > > Kai and Ismael, if you still feel this way, could you help me understand why? Since they don't seem to answer: 1. There is the "Application Menu" title bar button which technically counts as an exported menu bar but does not have any of the advantages of a traditional menu bar. Users might use it just to get rid of menu bars in applications. The bottom line is that we cannot count on the user actually wanting to use the exported menu bar. They might still want to use KHamburgerMenu even though they technically have an exported menu bar. (This is the reasoning behind Kai's commit message https://invent.kde.org/frameworks/kconfigwidgets/-/commit/901b049ca48e35fe9df07092a8657b1578fad300 and my comment on the related MR https://invent.kde.org/frameworks/kconfigwidgets/-/merge_requests/46#note_243184) 2. IIRC Ismael argued slightly differently. He does have an exported menu bar, but he typically still enjoys using the curated list of actions the KHamburgerMenu provides. I think he said that he likes using the more minimal UI within the window and the exported menu bar is there just in case. -- You are receiving this mail because: You are watching all bug changes.
