Description: UI Checkbox properties window black (Skia) white (OpenGL) Steps to Reproduce: 1. Open Writer 2. Insert a checkbox (Form) 3. Double click it -> Checkbox Control 4. Scroll down to tristate & change it -> Dialog black/or white Actual Results: Dialog not properly rendered Expected Results: Proper layout Reproducible: Always User Profile Reset: No Additional Info: Version: 7.0.0.0.alpha0+ (x64)Build ID: 8c8b3a4f83f67882b284ddc3b3fe10d3fe6dedf4CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: GL; VCL: win; Locale: nl-NL (nl_NL); UI-Language: en-USCalc: CL
Thank you for reporting the bug. I can confirm the bug present in Version: 6.4.0.0.alpha1+ (x86) Build ID: ec7374ff84c71edfbb30d6e4dc5b486b6df7107f CPU threads: 2; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: default; VCL: win; TinderBox: Win-x86@42, Branch:master, Time: 2019-11-10_21:37:30 Locale: en-US (en_US); UI-Language: en-US Calc: threaded
Dear Telesto, 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
Still present Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 4659fc2f0a7223a89446edff0b77e58758b5edf5 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL
Reproduced in daily master build: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 1ec2e39cf4d5fe0a592bc783fd8bcdc4345c8cbd CPU threads: 6; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded Version: 7.0.3.1 (x64) Build ID: d7547858d014d4cf69878db179d326fc3483e082 CPU threads: 6; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL
Bibisected win64-7.0. Added Caolán McNamara to cc. Regression introduced in commit: https://git.libreoffice.org/core/+/1efeb17837c22499f00299c033ae59ba3910f7d7 --------------------- commit 1efeb17837c22499f00299c033ae59ba3910f7d7 [log] author Caolán McNamara <caolanm@redhat.com> Mon Nov 04 13:06:04 2019 +0000 committer Caolán McNamara <caolanm@redhat.com> Mon Dec 09 13:28:35 2019 +0100 tree a8db0b758e942b3b14fba26129dc51a95ff5c10c parent 4da3e0a0e5b2260c26186890724978bfd00f796c [diff] ---------------------- f7cdd32887fa614c27fc4ee36e977bc85d0d268f is the first bad commit commit f7cdd32887fa614c27fc4ee36e977bc85d0d268f Author: Norbert Thiebaud <nthiebaud@gmail.com> Date: Mon Dec 9 04:57:38 2019 -0800 source 1efeb17837c22499f00299c033ae59ba3910f7d7
*** Bug 160132 has been marked as a duplicate of this bug. ***
Coming from duplicate bug 160132: Also seen e.g. in a Base form, with a Combo Box control, changing "Control Properties > Data > Type of list contents" from "sql" to "table". Also reproduced with the Form Properties dialog (changing the "Content Type"), and for a List Box control. Hovering over fields refreshes them, or changing tabs, refreshes the view. - Version: 7.5.0.3 (X86_64) - Version: 24.2.1.2 (X86_64) - Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 26f7313f724921a9c6086e6c2a93fbe1c48635fa CPU threads: 4; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded Not reproduced with Skia off: Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community CPU threads: 4; OS: Windows 10.0 Build 22631; UI render: default; VCL: win Nor on Linux: Version: 24.2.2.1 (X86_64) / LibreOffice Community CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: x11 ...but I did notice a change in item spacing when changing the "type of list content" value, even though the items don't change.
This one is odd, not reproducible on Linux with gen and skia enabled, but can be on Windows. Debugging into it, at OBrowserListBox::valueChanged, m_pLineListener->Commit(rLine.pLine->GetEntryName(), impl_getControlAsPropertyValue(rLine)); seems to be relevant to the oddity. wrt. "I did notice a change in item spacing when changing the "type of list content" value, even though the items don't change." I see that the last row, the "List Content" row changes from a plain Edit to an Edit + Button with "..." in it, and presumably the button is taller than the Edit, and presumably the rows are set to be the same height, so toggling "Type of list contents" ends up toggling the height of all rows. But that's probably isn't a trigger for the main strange drawing issue.