Description: The location of the active region of a hyperlink is inaccurate when - a spreadsheet is scaled, and - a cell contains long text (such as a dozen words) before a hyperlink. - the cell is not being edited. (I'm using 'active region' to name the region where the cursor turns into a hand and where control-click will follow the hyperlink.) There is no error if the cell is scaled to 100%. There is error when the spreadsheet is zoomed out to 65% or zoomed in to 200%. The direction of the error is the same for both shrinking to 65% and expanding to 200%: both shift the region to the left. If the cell is not wrapped, then the active region will be a bit to the left. If the cell is wrapped, then the active region may be at the end of the previous line. (Guess: Maybe the scaled region location calculation is truncating fraction bits, so the sum of scaled letter widths may become too small both when scaling up and when scaling down.) There is no error while the cell is being edited, so a correct algorithm is known. Steps to Reproduce: 1. Open attached spreadsheet "HyperlinkRegionInaccurateInScaledSheet.ods" (The initial scale should be 65%. If not, change the scale to 65% with the slider at the lower right.) 2. Hover the mouse near the hyperlink of the word "end" in cell A1. Actual Results: Cell A1: At 65% magnfication, cursor turns to hand over 'RY' of 'VERY'. At 200% magnification, cursor turns to hand over 'Y e'. At 100% magnification, cursor turns to hand over 'end', correctly. F2 in A1 to edit cell, then 'end' is highlighted correctly at all magnifications. Cell B1: At 65% magnification, if the cell is wrapped, then cursor may turn to hand at the end of the previous line, not near the word 'end'. Expected Results: In each scale, the cursor should turn to a hand when it hovers over the word 'end'. Reproducible: Always User Profile Reset: No Additional Info: Version: 6.2.3.2 (x64) Build ID: aecc05fe267cc68dde00352a451aa867b3b546ac CPU threads: 2; OS: Windows 6.1; UI render: default; VCL: win; Locale: en-US (en_US); UI-Language: en-US Calc: threaded Also reproduced in Version: 6.3.0.0.beta1 (x64) Build ID: a187af327633f5f00363be5131bd21a13e0f1a7b CPU threads: 2; OS: Windows 6.1; UI render: default; VCL: win; Locale: en-US (en_US); UI-Language: en-US Calc: threaded
Created attachment 151999 [details] sample demonstrating bug when scaled to 65% or 200%
I can confirmwith Version: 6.4.0.0.alpha0+ Build ID: 9712f5d2316fa469b92f2f8092925e2cd4e8dd5b CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: x11; and Version 4.1.0.0.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a)
Dear gekacheka, 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
Bug still present. Version: 7.1.4.2 (x64) / LibreOffice Community Build ID: a529a4fab45b75fefc5b6226684193eb000654f6 CPU threads: 8; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc:
Dear gekacheka, 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
Confirmed problem is still present. Version: 7.5.5.2 (X86_64) / LibreOffice Community Build ID: ca8fe7424262805f223b9a2334bc7181abbcbf5e CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded