Created attachment 121783 [details] Font comparison On master and LO 5.1, UI on Windows has decayed. I noticed 3 problems, maybe there is more. 1. (strange glitches) Selected tab in dialogs has lost its borders. Check marks in menus have lost their borders. 2. (annoying bug) Open a menu, then slide to other menus. On LO 5, rendering of menus is fast and is done instantly. On LO dev, rendering is slow and we see empty menu before the content is being displayed. 3. (very important bug) Font rendering has decayed. If you are not a daily Windows user, you may not notice it immediately, but it strikes me as soon as I opened the window. (See attachment.) It is particularly visible on letters “v” and “w”. But the whole rendering is not as neat on LO dev than on LO 5.
Created attachment 121784 [details] UI-glitches
Please NEVER cram multiple issues in a single bug report. Thanks. > Selected tab in dialogs has lost its borders Already known; it’s bug 95618. > Check marks in menus have lost their borders. Let’s make this report focus on that. > rendering is slow and we see empty menu before the content is being displayed Again, known. Please disable OpenGL in the settings as a workaround. > Font rendering has decayed That’s your opinion. It’s just a different setting of Windows’ DirectWrite, as compared to the older GDI+ rendering. It hasn’t “decayed” nor it’s an actual issue. The newer rendering is also implemented in modern Windows apps.
Marco - can you look at the check-box issue here - I imagine it is another example of that state not being included in the native widget theme / texture cache key (we need that fixed generically :-) Thanks !
Since we have a bibisect repository for windows covering the branch where this regression was introduced, adding keyword 'bibisectRequest'. More info: https://wiki.documentfoundation.org/QA/Bibisect/Windows
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.4.1 or 5.3.6 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170929
Still reproduced in LO 5.4.3.2. Already there in LO 4.4.0.3, adjusting earliest version. Removing regression-related keywords, as no known good version has been reported. That was the check mark issue. For font rendering with OpenGL, probably bug 107521 is relevant, see bug 107521 comment 21.
(In reply to Michael Meeks from comment #3) > Marco - can you look at the check-box issue here - I imagine it is another > example of that state not being included in the native widget theme / > texture cache key (we need that fixed generically :-) SAL_WITHOUT_WIDGET_CACHE=1 leaves this unchanged, but SAL_NO_NWF=1 works the problem around, so I guess it's more like we use something in the Windows NWF code that is not supported by the opengl backend. I'll try to find out what is that.
Miklos Vajna committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=b160db926b574b7e9d6696d49dbbce8dd289aade tdf#96947 vcl opengl win: fix background of menu items w/ check/radio marks It will be available in 6.1.0. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Miklos Vajna committed a patch related to this issue. It has been pushed to "libreoffice-6-0": http://cgit.freedesktop.org/libreoffice/core/commit/?id=96bb95e64240ddeb59d623d62fa30b2a7191bfc4&h=libreoffice-6-0 tdf#96947 vcl opengl win: fix background of menu items w/ check/radio marks It will be available in 6.0.5. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
The fix for this caused a regression in FontWork menus which have both Check marks and radio buttons in the menu. See Bug 119947