Description: LO could use screen space more efficiently, which is a major concern to many of us, especially when using small screens or prefer a more focused writing environment. At the moment, the menu bar can be toggled on/off through an optional toolbar button. Annoyingly, when you restart LO the menu bar is always visible (possibly, in case users lose it and panic). It would be better if (a) there was an option to make the menu bar invisible on start by default (b) we were able to toggle it on by quick-pressing just 'Alt' as it is common in many applications (eg Firefox, Thunderbird, notepad++) (c) we could optionally reduce the menus to a hamburger button with menus dropping vertically, making the menu bar redundant. These would save valuable vertical space by removing the menu bar permanently or most of the time, decluttering the screen. Steps to Reproduce: 1. Add a toolbar button for the 'menu toolbar' 2. Hide the menu toolbar 3. Restart LO Actual Results: The menu toolbar is visible on restart. The only way to hide it again is to click on the menu button. Expected Results: The menu toolbar should remain invisible until I pressed 'Alt'. Reproducible: Always User Profile Reset: No Additional Info: A hamburger button revealing vertically the complete menu structure would make the menu toolbar and the above 'Alt' mechanism optionally redundant.
(In reply to Uncombed5936 from comment #0) > Annoyingly, when you restart LO the menu bar is always visible... If this has not been reported it is worth an extra ticket. > It would be better if (a) there was an option to make the menu bar invisible > on start by default The majority of users would likely disagree, at least in case of the standard UI. (b) we were able to toggle it on by quick-pressing just 'Alt' Yes, but dup of bug 107358
Visibility of the Main menubar depends on the UI selected. And the .uno:Menubar action is available to assign by 'Customize...' dialog to any menu, keyboard shortcut, toolbar button, context menu, or even its Notebookbar checkbox toggle. Several of the MUFFIN assemblages have the Main menubar disabled by default, though our default/legacy "Menu & Toolbar w/Sidebar deck" UI mode simply has it enabled by default. One suggestion in bug 90195 and bug 107343 is to overload the <F10> main menu focus necessary for accessibility (where F10 and F6 movements are reserved). Conversely the <Alt> visibility toggle destroys keyboard navigation, so while considered (during bug 90195 workup) it was not really pursued as it would have broken keyboard navigation and accessibility. That has not really changed, the <Alt> toggle remains not really appropriate to the UI for all users. What would be useful, would be persistence per module recorded to user profile, setting the main menubar visibility status. So that once user configures visibility of the main menu in a module, setting remains like on subsequent launches. The visible/hidden toggle should be oveloaded onto the <F10> by default as per bug 107343, with user choice to customize any additional controls for the UNO toggle. Leave the <Alt> behavior alone, where it already appropriately controls toggle of mnemonic key accelerators. And is a clear => WF to toggle visibility of the main menubar.
With the standard menu/toolbar set-up, the hidden state of the menu bar is not remembered between sessions. The menu bar reappears on start-up. I suggested that keeping the menu bar hidden would be an option -- not all users have to agree either way. I don't see how the Alt method interferes with other functions or accessibility. Alt unhides temporarily the menu bar in Firefox, Thunderbird, notepad++ etc when it's not combined with another key. You just press Alt and release. That's why I said "quick-pressing just 'Alt'". That doesn't interfere with Alt+key combinations. It is a very efficient and increasingly common way to reveal the menu bar, and keep it hidden to declutter when the bar is not needed. If I have to press F10, I might as well click on the menu button on the toolbar. Or Alt vs F10 vs whatever else could be configurable. But a hamburger button showing the menus vertically could be another or a better idea. I don't see why we couldn't have a button like this that we could add to the standard toolbar and optionally make the menu bar hidden by default in all layouts. If I could have all menus in a standard toolbar button, I would never switch on the menu toolbar again, which would save me some vertical space permanently and the environment would look cleaner too.
(In reply to Uncombed5936 from comment #3) > ... > But a hamburger button showing the menus vertically could be another or a > better idea. I don't see why we couldn't have a button like this that we > could add to the standard toolbar and optionally make the menu bar hidden by > default in all layouts. If I could have all menus in a standard toolbar > button, I would never switch on the menu toolbar again, which would save me > some vertical space permanently and the environment would look cleaner too. Hmm, interesting MUFFIN idea! Full main menu expanding as a list box with nested sub-menus. See one issue immediately for keyboard navigation of a "vertical" menubar UI imposing a shift in cursor movement orientation. Ugly to try to map Up/Down and Left/Right to a 90° rotation. But once adopted users would adjust. Hmm...