Bug 107363 - Grouped buttons doesn't become properly disabled
Summary: Grouped buttons doesn't become properly disabled
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
(earliest affected)
Hardware: All All
: medium normal
Assignee: Not Assigned
Depends on:
Blocks: Notebookbar Read-Only
  Show dependency treegraph
Reported: 2017-04-23 07:40 UTC by Heiko Tietze
Modified: 2021-03-21 18:02 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:
Regression By:


Note You need to log in before you can comment on or make changes to this bug.
Description Heiko Tietze 2017-04-23 07:40:37 UTC
For example, the grouped sections variant of the Notebookbar contains of a Link button with some underlying options. But when a write-protected document is loaded, e.g. downloaded from the internet, this button with all children is not disabled properly. The function itself is not accessible meaning the dialog does not opens on click.
Comment 1 Heiko Tietze 2017-04-23 07:45:34 UTC
Confused myself with LibO fresh where this button was just a dummy. In master the menu is cleared and "<no selection is possible>" shown. The button itself is enabled (otherwise the menu may not be opened).

We can keep the current behavior. It's only a minor confusion that menu buttons are shown without content / when all content is disabled.
Alternatively, if no function is left the group itself could be disabled.
Comment 2 QA Administrators 2018-04-24 02:33:05 UTC Comment hidden (obsolete)
Comment 3 andreas_k 2018-12-08 23:51:45 UTC
I can confirm this bug, but as Heiko wrote for me it's also a small visual issue.
Comment 4 QA Administrators 2019-12-09 03:38:48 UTC
Dear Heiko Tietze,

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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team