Description: In consistent cursor after using find & replace (and with undo/redo of the replacement) Steps to Reproduce: 1. Open the attached file 2. Drag the mouse from He to the question mark (cursor at the end of the paragraph) 3. CTRL+H 4. Find: "." 5. Replace: x 6. Current selection only 7. Replace all 8. Close using red cross 9. Cursor 1 to left 10. Press Undo 11. Press redo (Cursor placed between "He" 12. Place the cursor at the end the paragraph (without a selection 13. Press CTRL+H 14. Find: "." 15. Replace: x 16. Replace all 17. Close.. cursor still at same spot 18. Undo CTRL+Z (cursor between "He") 19. Redo CTRL+Y (cursor one to the left) Actual Results: Cursor position isn't really consistent Expected Results: Some consistency. In my opinion: * Not between "He" * Not a different position on redo * Choose a ending position (?) or at the end of the sentence. Reproducible: Always User Profile Reset: No Additional Info: Version: 6.2.0.0.alpha0+ Build ID: c0fdcece6b886912618deee9656cb2d169a9b999 CPU threads: 4; OS: Windows 6.3; UI render: default; TinderBox: Win-x86@42, Branch:master, Time: 2018-08-12_00:35:45 Locale: en-US (nl_NL); Calc: CL
Created attachment 144304 [details] Sample file
I tested it. I supose it is working ok, but it is shown wrong after "he". Versiune: 6.0.3.2 Identificator construire: 1:6.0.3-0ubuntu1 Fire CPU: 4; OS: Linux 4.15; Redare UI: implicit; VCL: gtk3; Setări regionale: ro-RO (ro_RO.UTF-8); Calc: group
Repro. Arch Linux 64-bit Version: 6.2.0.0.alpha0+ Build ID: 05db125c57ea3c8f04a304561209c32cc5c45a67 CPU threads: 8; OS: Linux 4.18; UI render: default; VCL: gtk3_kde5; Locale: fi-FI (fi_FI.UTF-8); Calc: threaded Built on September 17th 2018
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 http://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
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://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
I don't see a bug nor value in changing this so I close. If someone disagrees, please be exact what is wrong and expected.