Description: When you drag, without releasing, a sheet-tab in the tab deck at the bottom of a Calc window, and move it around over the other tabs, guiding triangles |> <| show up to indicate where the tab will be placed if you release it. However - when these triangles are re-painted, as you move your mouse - some pixels remain painted black when they should have been cleared. A comparison of screenshots will follow. Steps to Reproduce: 1. Open a new LTR document with LTR UI. 2. Add several sheets, to have, say, 5 sheets in total. 3. Select the first (leftmost) sheet-tab, with you mouse - keeping the mouse button down. 4. Drag the tab slowly to different positions in the tab deck, back-and-forth Actual Results: You always see at most one pair of triangles, and no "vestigial" black triangle pixels from previously-appearing triangle pairs. Expected Results: You see pixels from previously-painted triangles where the triangles are no longer present. Reproducible: Always User Profile Reset: No Additional Info: Observed with: Version: 7.1.0.3 / LibreOffice Community Build ID: f6099ecf3d29644b5008cc8f48f42f4a40986e4c CPU threads: 4; OS: Linux 5.9; UI render: default; VCL: gtk3 Locale: he-IL (en_IL); UI: en-US Calc: threaded Note that there are also issues with tab dragging and triangle painting in the context of RTL UI and/or RTL sheets. This is a different issue, although there might be some relation.
Created attachment 169744 [details] Cropped screenshots: While dragging a tab vs before dragging
confirm in Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: ac80ec817eb07c77a51bc0729985a473c734182e CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Vulkan; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: threaded
Dear Eyal Rozenberg, 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
Note: The opening comment mixed up the actual and expected results. Obviously we expect not to get repainting artifacts, but we do get them. Problem persists with: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 5cd9de202765e243e41416802f3e4486b8a96f16 CPU threads: 4; OS: Linux 6.1; UI render: default; VCL: gtk3 Locale: he-IL (en_IL); UI: en-US
Created attachment 188819 [details] Screenshot of behavior as of LO 7.6a