Description: If I am typing in insert mode with "autocorrect while typing" turned on, and then I undo an autocorrect, the cursor stays at the point at which I was typing, which is the correct behavior. If, however, I am typing in overwrite mode with "autocorrect while typing" turned on, and then I undo an autocorrect, the cursor bounces back to the *beginning* of the undone text. In order to return to the place where I was typing, I have to hit "end" or ctrl-arrow. This seems like it must be a bug, but if intentional, I can't fathom why the decision was made. What about undoing an autocorrect in overwrite mode would suggest returning the cursor to the beginning of the undone text? This has real productivity-impairing ramifications: if I am editing a line of text in overwrite mode and insert a space after text that gets autocorrected and undo it, I have to hit an additional keystroke (end or ctrl-arrow) to get back to where I was before. Steps to Reproduce: 1. Make sure the cursor is in insert mode. 2. Make sure that Tools | Autocorrect | While Typing is checked. 3. Type some text that will get autocorrected, e.g., 1/2 followed by a space. 4. Hit undo. Notice that the text reverts to 1/2 and the cursor stays at the space you typed after the 1/2. 5. Delete the space. The cursor should now be after the 2. 6. Change to overwrite mode. 7. Hit space. 1/2 should now be autocorrected. 8. Hit undo. Notice that the cursor jumps back to the 1. Actual Results: Cursor jumps back to the beginning of undone autocorrected text. Expected Results: Cursor should stay put at the space afterwards. Reproducible: Always User Profile Reset: No Additional Info: Version: 7.6.4.1 (X86_64) / LibreOffice Community Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1 CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded
Confirm with Version: 7.6.2.1 (X86_64) / LibreOffice Community Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333 CPU threads: 16; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded
Dear William Friedman, 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