Description: I am running LibreOffice 7.0.3.1 on Linux Mint 20 Cinnamon. I am a big fan of the new option to hide the menu bar in the Writer app via `View > [ ] Menubar`. I would like to use it with the Single Toolbar UI but unfortunately my preference resets every time I re-launch Writer. I understand that this is done by design as, by default, the toolbar does not have a show/hide menubar icon (I have added one to mine). Most software that have an option for hiding the menu bar implements a standard shortcut to show it at any time when hidden; all you have to do is hit the `Alt` key and the menu bar will show up momentarily when hidden. Hitting `ESC`, `Alt` again, or clicking outside the menubar will hide it once more. This is how the hidden menubar is implemented in Firefox, Thunderbird, Nemo, Atom, Typora, among many others. Steps to Reproduce: 1. Customise Single or Standard Toolbars by adding a Menubar icon to them 2. Click on the icon to hide the menubar 3. Restart the application Actual Results: Menubar is back being shown at the next startup Expected Results: User preference for hidden menubar would be kept between sessions. This might require implementing the standard `Alt` shortcut as described in this report's description. Reproducible: Always User Profile Reset: No Additional Info: From the discussion: https://ask.libreoffice.org/en/question/281406/hiding-menu-bar-permanently/
(In reply to gilbertohasnofb from comment #0) > I am running LibreOffice 7.0.3.1 on Linux Mint 20 Cinnamon. I am a big fan > of the new option to hide the menu bar in the Writer app via `View > [ ] > Menubar`. There is no such menu "View > [ ] Menubar" option by default. You must have done a customization to get this available in your menu.
Sorry, you are right. I customised both the toolbar and the View menu. But the steps I described to reproduce it are still correct. Regardless of this customisation, implementing the Alt shortcut would allow the menubar to be hidden in any UI mode as there would not be any danger of an user not being able to access it.
For GSOC 2016 work on the Notebook Bar an UNO toggle control was provided [1] and is integral to the MUFFIN modes, but as noted for bug 90195 it was not assigned a short-cut. When I customize the Writer View menu and add the .uno:MenuBar toggle it will persist for the 'Contextual Single' mode. But not for Standard or Single as noted. So try with Contextual Single (IMHO its hybrid handling of context sensitive elements makes it the best of the MUFFIN assemblages). IMHO the better customization than a View menu assignment is to assign a keyboard shortcut to the toggle control. I find <Atl>+<Ctrl>+F10 easy to work with, and the shortcut is essential for UI mode where you are unable to exit without the main menu. There is still some question as to a11y support, that the <F10> alone should expose the main menu to position the UI to a consistent place -- bug 90195, bug 107343 But this is => NAB Otherwise there is no benefit cross platform to overloading <Esc>/<Alt> for main menu handling, and as enhancement would be a clear => WF =-=ref-= [1] https://gerrit.libreoffice.org/c/core/+/28044
(In reply to V Stuart Foote from comment #3) > But this is => NAB We want to keep the user choice and I don't see a workflow where hiding the menubar would be desired only temporary. Also for classic UIs. Even with the bug 107343 we would need to make it persistent.
Dear gilbertohasnofb, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Hi, bug is still present in current version. Information from About LibreOffice: Version: 7.4.2.3 / LibreOffice Community Build ID: 40(Build:3) CPU threads: 12; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-GB (en_GB.UTF-8); UI: en-GB Ubuntu package version: 1:7.4.2~rc3-0ubuntu0.20.04.1~lo1 Calc: threaded (In reply to QA Administrators from comment #5) > Dear gilbertohasnofb, > > To make sure we're focusing on the bugs that affect our users today, > LibreOffice QA is asking bug reporters and confirmers to retest open, > confirmed bugs which have not been touched for over a year. > > There have been thousands of bug fixes and commits since anyone checked on > this bug report. During that time, it's possible that the bug has been > fixed, or the details of the problem have changed. We'd really appreciate > your help in getting confirmation that the bug is still present. > > If you have time, please do the following: > > Test to see if the bug is still present with the latest version of > LibreOffice from https://www.libreoffice.org/download/ > > If the bug is present, please leave a comment that includes the information > from Help - About LibreOffice. > > If the bug is NOT present, please set the bug's Status field to > RESOLVED-WORKSFORME and leave a comment that includes the information from > Help - About LibreOffice. > > Please DO NOT > > Update the version field > Reply via email (please reply directly on the bug tracker) > Set the bug's Status field to RESOLVED - FIXED (this status has a particular > meaning that is not > appropriate in this case) > > > If you want to do more to help you can test to see if your issue is a > REGRESSION. To do so: > 1. Download and install oldest version of LibreOffice (usually 3.3 unless > your bug pertains to a feature added after 3.3) from > https://downloadarchive.documentfoundation.org/libreoffice/old/ > > 2. Test your bug > 3. Leave a comment with your results. > 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; > 4b. If the bug was not present in 3.3 - add 'regression' to keyword > > > Feel free to come ask questions or to say hello in our QA chat: > https://web.libera.chat/?settings=#libreoffice-qa > > Thank you for helping us make LibreOffice even better for everyone! > > Warm Regards, > QA Team > > MassPing-UntouchedBug