Description: When trying to select an entire line or a column in a table in writer on Apple Mac, the cursor changes to an arrow and jumps down and to the right. This results in the mouse click not happening where the arrow is pointing, but several points above it to the left. Most obvious on line because columns are usually wider. Steps to Reproduce: 1. Make a table with several lines (about 9points high) and columns in Writer on Apple Mac 2. Hover at the front of the first cell on the second or lower line of the table to select the entire line 3. Observe the cursor change from the I to an arrow and jumping down and to the left. Click on the mouse and see what is selected at various heights of the cell. Actual Results: When the arrow is at the top half of the cell, the clock will not select that line, but the one above it. Expected Results: It should select the line the arrow is pointing at. Reproducible: Always User Profile Reset: No Additional Info: Utterly explained and small videoclip in one of my comments here: https://ask.libreoffice.org/en/question/287343/bug-row-and-column-selection-arrows-in-tables-weird-writer-on-mac/
*** Bug 141451 has been marked as a duplicate of this bug. ***
Confirming mouse pointer wonkyness when using a table with empty lines above and moving slowly over the table. Mouse pointer jumps unexpectedly. Version: 7.1.2.2 / LibreOffice Community Build ID: 8a45595d069ef5570103caea1b71cc9d82b2aae4 CPU threads: 4; OS: Mac OS X 10.15.7; UI render: default; VCL: osx Locale: de-DE (de_DE.UTF-8); UI: en-US Calc: threaded
Also on Linux: Version: 7.5.0.1 (X86_64) / LibreOffice Community Build ID: 77cd3d7ad4445740a0c6cf977992dafd8ebad8df CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded and: Version: 6.3.6.2 Build ID: 2196df99b074d8a661f4036fca8fa0cbfa33a497 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3; Locale: en-AU (en_AU.UTF-8); UI-Language: en-US Calc: threaded It's a regression as 6.2 didn't have the issue: Version: 6.2.0.0.beta1 Build ID: d1b41307be3f8c19fe6f1938cf056e7ff1eb1d18 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3; Locale: en-AU (en_AU.UTF-8); UI-Language: en-US Calc: threaded The Show/Hide Whitespace cursors do the same thing (test by hovering over the space between two pages). But I think it should be reported separately as they were already offset in 6.2.
(In reply to Stéphane Guillou (stragu) from comment #3) > > It's a regression as 6.2 didn't have the issue: > Stepháne, can you bisect it? I doesn't see the issue..
Bibisected with linux-64-6.3 repo to first bad commit 226a563bc37c76a9cc7a73b12ebac4018d51c017 which points to core commit: commit 25d176ada67ada550bd4d0d08177c232cf7eeb37 author Noel Grandin <noel.grandin@collabora.co.uk> Mon Mar 04 15:58:18 2019 +0200 committer Noel Grandin <noel.grandin@collabora.co.uk> Tue Mar 05 08:17:32 2019 +0100 tree 4c01c298782fd88b8764c083697066cb0962af4b parent ac69149beff331755be67220a85a2e7b0644384f tdf#123796 Wrong cursor when inserting shape regression from commit c5ac80d90ebcc1c3fad18ece8784ac2b36f52045 make cursor images part of the theme Turns out that I can't put SVG files into a normal theme, only colibre_svg is allowed to contain SVG files, so my idea of having only one set of files is not going to fly. So make a copy of the PNG files into the colibre theme, which is what everything currently falls back to. Change-Id: I5f04226da5c8b3d5db7e9807e845112b76b72f22 Reviewed-on: https://gerrit.libreoffice.org/68695 Noel fixed an issue with the wrong pointer being used (bug 123796), which was a regression from c5ac80d90ebcc1c3fad18ece8784ac2b36f52045, but the fix has the offset/jump observed here. Noel, can you please have a look?
Dear Dutch, 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
*** Bug 163916 has been marked as a duplicate of this bug. ***