KDE is an international technology team creating user-friendly free and open source software for desktop and portable computing. KDE’s software runs on GNU/Linux, BSD and other operating systems, including Windows.
If you encounter a bug, proceed to https://bugs.kde.org, check whether it has been reported.
If it hasn't, report it yourself.
PLEASE THINK CAREFULLY BEFORE POSTING HERE.
Developers do not look for reports on social media, so they will not see it and all it does is clutter up the feed.
Since I discovered the existence of global menu on Plasma, I've been searching for a version of Firefox that supports it. While I've found patches for it, I don't know if it still works and have the patience to compile it.
Kudos if it's in the AUR pre-compiled.
If you don't know what global menu is it just moves the toolbar to any panel you want like in the attachment.
EDIT: Compiled firefox-globalmenu from the AUR, turns out it doesn't work with wayland :(
@gnawmon I gave up using global menu on any linux desktop environment long time ago. Sadly, many apps don’t handle it, and it’s not the same experience like in macOs.
What do you like about it in macOS? I have never used it, so it's hard for me to understand the appeal.
In macOS it makes it very clear which application you’re in (if you momentarily forget), and you can get to menu items quickly (if you’re not already using the consistent key commands already) especially when using a Magic Trackpad (just swipe down fast and you’re there).
Whenever I have to deal with looking at Windows, application windows look super clunky and it’s definitely not helped by windows duplicating inconsistent menus everywhere.
Have you seen Safari on macOS? Other browsers have to settle for hiding everything under a hamburger menu or gear icon, making the inconsistent non-native UI problem more apparent.
@mearce There's only one thing I like in it: it saves space. Usually, you have a plenty of free space in panels. You can use a bit of this space for a global menu.
@mearce You are used to windows being either Maximized or Fullscreen, and these two states being very different things, and changing from one to the other being an hassle, especially exiting from Fullscreen requires touching the keyboard (ESC or f11), or a special button in the interface, hoping the developer made it recognisable. In reality, they are the same thing, with the only difference that Fullscreen hides the menus. If you have the global menu attached to a menu that avoids maximized windows you have unified Fullscreen and Maximized. If on the same panel you also put a widget tonexit from maximized, you also have a universal way to exist from Fullscreen: just take the cursor to the top of the screen and reveal the panel.