[upstream] Status of togglable menu entries is very hard to distinguish with gen VCL plugin

[White_Rabbit]

Some buttons like "Snap to Snap Guides" can be toggled, but it's very hard to understand in which status they are.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libreoffice (not installed)
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: LXDE
Date: Fri Nov 16 12:21:50 2018
InstallationDate: Installed on 2018-10-31 (15 days ago)
InstallationMedia: Lubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: libreoffice
UpgradeStatus: No upgrade log present (probably fresh install)

[Olivier Tilloy (osomon)]

Confirmed, the outline around the icon is almost invisible, making it really hard to tell whether the option is checked.

This is with the generic VCL plugin. This can be observed on a stock ubuntu desktop by running:

    SAL_USE_VCLPLUGIN=gen libreoffice --draw

[Olivier Tilloy (osomon)]

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:

[Olivier Tilloy (osomon)]

I reported the bug upstream: https://bugs.documentfoundation.org/show_bug.cgi?id=121461.

[Xiscofauli (xiscofauli)]

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...

[White_Rabbit (radiocane)]

As a workaround I installed libreoffice-gtk3 as per https://askubuntu.com/questions/285089

[Qa-admin-q (qa-admin-q)]

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

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

Warm Regards,
QA Team

MassPing-UntouchedBug

[Qa-admin-q (qa-admin-q)]

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