Bug 121461 - Status of togglable menu entries is very hard to distinguish with gen VCL plugin
Summary: Status of togglable menu entries is very hard to distinguish with gen VCL plugin
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
5.2 all versions
Hardware: All Linux (All)
: lowest trivial
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Snap
  Show dependency treegraph
 
Reported: 2018-11-16 12:35 UTC by Olivier Tilloy
Modified: 2024-12-14 14:28 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Olivier Tilloy 2018-11-16 12:35:57 UTC
Description:
(initially reported in Ubuntu: https://launchpad.net/bugs/1803696)

Some menu items like "Snap to Snap Guides" can be toggled, but it's very hard to understand in which status they are because the outline around the icon is almost invisible.

Steps to Reproduce:
Run LibreOffice Draw with SAL_USE_VCLPLUGIN=gen, toggle the "View > Snap Guides > Snap To Snap Guides" menu item.

Actual Results:
When re-opening the "View > Snap Guides" menu, it is very hard to tell whether the "Snap To Snap Guides" entry is checked or not. When it is checked, there is a thin, almost invisible outline around the icon.

Expected Results:
When re-opening the "View > Snap Guides" menu, it is obvious whether the "Snap To Snap Guides" entry is checked or not.


Reproducible: Always


User Profile Reset: No



Additional Info:
Comment 1 Xisco Faulí 2018-12-18 15:51:34 UTC
Reproduced in

Version: 6.3.0.0.alpha0+
Build ID: 6dc36d343aeacb3d1e14ec0c847937d63f4e68a7
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: x11; 
Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US
Calc: threaded

and

Version: 5.2.0.0.alpha0+
Build ID: 3ca42d8d51174010d5e8a32b96e9b4c0b3730a53
Threads 4; Ver: 4.15; Render: default;

this is only in gen, setting importance to lowest...
Comment 2 QA Administrators 2020-12-18 03:50:44 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2022-12-19 03:18:22 UTC
Dear Olivier Tilloy,

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