Description: Unwanted scroll to cursor when closing /existing highlighting bucked pressing ESC with cursor on different page Steps to Reproduce: 1. Open attachment 163710 [details] 2. Scroll down (single page or multi page view) (don't change the cursor position) 3. Click the highlighting bucked in the toolbar 4. Press ESC A user case.. you're scrolling through a document.. highlighting stuff... you did it on page 5 the last time.. currently you're on page 10.. you notice.. nothing to highlight anymore. You press ESC. Jumping to page 5 If they last highlighting is on page 5, and you're on page 5 and press ESC nothing will change. So not seeing the object.. Currently ESC does 2 things.. disabling the bucket & causing a scroll (if the cursor is on a different page). Actual Results: Scroll to cursor Expected Results: Not so Reproducible: Always User Profile Reset: No Additional Info: Version: 7.1.0.0.alpha0+ (x64) Build ID: 52a49f9e480ca03e231cfda82640a928393131c9 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
Confirmed: The view jumps back to the caret (text cursor) position when pressing Esc or when clicking again on the Highlight Color button in toolbar/sidebar. The highlighting feature is special as it's not directly acting on the position of the caret (as for example the Bold button does - at the position of the caret or the selected text the bold feature begins to act) but where the user select text anywhere in a document. Tested with Version: 7.1.0.0.alpha0+ Build ID: a8c218a52a639b0e7f689dea878a0421702628e0 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3 Locale: de-DE (de_DE.UTF-8); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2020-09-25_22:25:07 Calc: threaded and Version: 6.0.7.3 Build-ID: 1:6.0.7-0ubuntu0.18.04.10 CPU-Threads: 4; BS: Linux 4.15; UI-Render: Standard; VCL: gtk3; Gebietsschema: de-DE (de_DE.UTF-8); Calc: group and LibreOffice 3.3.0 OOO330m19 (Build:6)
@Julien Any change to get you interested/motivated to solve some 'unwanted scroll' situations. It would be nice from usability point of view. The solution is apparently a one trick pony: https://bugs.documentfoundation.org/show_bug.cgi?id=135244#c12. Which apparently has to be applied on case by case basis :-( See (meta) bug 106773 for list of those (recent bugs surely present, older once might need a check). So as soon you start with this, their is some change for asking more (however I assume meta bug 106773 is covering the most of the ground). Mike got bit overwhelmed and bailed out ;-). See bug 135244. Note: if you consider to work on this, please take in consideration that some scroll being apparently allowed. And a report as such might be not enough. Mike has his system/model where it's allowed and where not. See bug 135244. I'm personally less tolerant to scrolling :-). And not totally convinced by Mike his vision, but lets tackle the stuff everybody agrees on first Of course, if this isn't your type thing.. pretend I never asked :-)
Taking a look at Mike's patches, I'm not expert enough to deal with locks so can't help here=>unassign myself.
@Caolan Any change to get you interested/motivated to solve some 'unwanted scroll' situations. It would be nice from usability point of view. I think. The solution is apparently a one trick pony: https://bugs.documentfoundation.org/show_bug.cgi?id=135244#c12. Which apparently has to be applied on case by case basis :-( See (meta) bug 106773 for list of those (recent bugs surely present, older once might need a check). Their is some change for asking more as happened in bug 135244. However I assume meta bug 106773 is covering the most of the ground). Mike got bit overwhelmed and bailed out ;-). Asked Julien, but he seems himself not expert enough to deal with locks.. so this might not be the easy hack I hoped it to be... FWIW: Mike has a certain logic about which scrolls are allowed and which not. Also bug 135244. Not sure if there a bug around which don't qualify. I'm personally not really big fan of scroll to cursor. So I see this more often as an issue compared to Mike. Anyhow, lets tackle the stuff where everybody agrees on first.. As always; feel free to ignore.. or place it in queue for some day in so year.. there is no rush
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