This happens when switching to a Notebookbar user interface from another user interface when document is read-only.
Steps to repro:
1) Open a text document
2) Set user interface to Standard Toolbar
Menu > View > User Interface > Standard Toolbar
3) Uncheck Menu > Edit > Edit Mode
4) Set user interface to any of the Notebookbar user interfaces, Tabbed, Tabbed Compact, Groupedbar Compact, Contextual Single
Results: Controls that should be shown disabled when document is read-only are shown as enabled.
Expected results: Controls that should be shown as disabled when document is read-only are shown as disabled.
Additional comments: Even though the controls are shown as enabled they are not functional.
I confirm it with
Version: 188.8.131.52.alpha0+ (x64)
Build ID: e26d89371f0e4f41476c9a99be01d98dedb76776
CPU threads: 4; OS: Windows 10.0 Build 18362; UI render: default; VCL: win;
Locale: de-DE (de_DE); UI-Language: en-GB
I am very happy to see this type article. it is very useful and exciting. the best blessings of this article is giving properly idea to each and every readers and also it's giving correct impressions. Looking forward to new article. I would like to use every topic from this website. In these topics I have found so many methods and they are making lot of services. Everything I have read from these blogs, and thanks for updating those services.
I'm under the impression that the only tabs/groups that should be enabled in read-only mode are the "File" and "View" tabs... everything else (Home, Insert, Layout, Data, Image, Forms, Review, and possibly "Extensions" and "Tools") typically requires write capability.
In that case, I'd suggest those tabs/groups to be hidden entirely, until the document becomes read+write; that way, it would keep the UI simpler and more contextualized for users.
Dear Jim Raykowski,
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!
The STR given in the OP still show the same results for:
Version: 184.108.40.206.alpha0+ (X86_64) / LibreOffice Community
Build ID: 770580ba8e9546aa7b960c8b622b936ba6cf9d37
CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: x11
Locale: en-US (en_US.UTF-8); UI: en-US