Description: When changing (or just reading the width of a column) the hover text shows different values as column width depending on the exact position of the mouse cursor. For example, for a column A of width 2.26cm it reads 2.20cm if the mouse points to the very left of the column boundary between columns A and B; it reads 2.31 if pointing to the very right edge of it. Steps to Reproduce: 1. Open a new document or any existing one. 2. Left mouse click and hold on the column separator. Actual Results: It reads 2.20cm if the mouse points to the very left of the column boundary between columns A and B; it reads 2.31 if pointing to the very right edge of it. Expected Results: It should read 2.26 cm, as that is the actual column width (checked by the "Column Width" dialog). Reproducible: Always User Profile Reset: No Additional Info: Version: 7.2.6.2 (x64) / LibreOffice Community Build ID: b0ec3a565991f7569a5a7f5d24fed7f52653d754 CPU threads: 8; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: hu-HU (hu_HU); UI: en-US Calc: threaded
Confirm wit Version: 7.4.0.0.alpha0+ / LibreOffice Community Build ID: ab8d141967111ca81f4607db3618bb09214e42db CPU threads: 4; OS: Linux 5.13; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded Jumbo I see no tooltip in Version: 7.0.0.0.alpha1+ Build ID: 574c57090642347980d2395e1e183cc7b5c171ad CPU threads: 4; OS: Linux 5.13; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded adding tag bibisectrequest for bibisect where tooltip was made.
Created attachment 179494 [details] video of the problem
This is actually not a regression, just due to GTK the popup wasn't shown for a while until Caolán fixed it in bug 133953. Otherwise, with eg. gen VCL plugin, the bug can be reproduced even in 3.3.
(In reply to Aron Budea from comment #3) > This is actually not a regression, just due to GTK the popup wasn't shown I meant to write tooltip instead of popup.
Dear roli.vincze, 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