When Enter key is pressed to form a new paragraph and that action causes autocorrection, like capital letter insertion, this action precedes the creation of the paragraph in Undo stack. In normal software, the autocorrection is undone first, then Enter key effect.
Confirmed. But still - how does this bug make LO not-normal software? :)
I do not understand what you mean because it is not hitting Enter key which causes "capital letter insertion" autocorrection but the insertion of a space after the first word of the new paragraph. I tried this: 1/ open a new empty text document 2/ type dt+F3 (autotext "dummy text") 3/ click at the end of the text and hit the Enter key 4/ type some word like "example" 5/ press the space bar example becomes Example 6/ press ctrl+Z ==> Example becomes example 7/ press ctrl+Z ==> space after "example" removed 8/ press ctrl+Z ==> the word example is removed 9/ press ctrl+Z ==> the new paragraph is removed Tested with versions 4.0.6, 4.1.4 and 4.2.0.1+ under Ubuntu 13.10 x86-64 with each time the same result. I propose to close this bug report as WorksForMe Best regards. JBF
Do not press Space, press Enter, as described.
(In reply to comment #3) > Do not press Space, press Enter, as described. Do you mean press Enter key after the first word in the new paragraph ? Best regards. JBF
(In reply to comment #4) > (In reply to comment #3) > > Do not press Space, press Enter, as described. > > Do you mean press Enter key after the first word in the new paragraph ? > > Best regards. JBF Yes, that's what he meant: press enter in your step 5) This bug is really quite annoying, and resulted in my disabling most of auto-corrections, as it makes them do more harm than good. I understand that you could argue this behavior works "as intended", except that if it is so, the behavior should be the same with both "space" and "enter", which is not the case. So it's definitely a bug (not an enhancement as suggested in Bug 44062).
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.0.0.5 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-09-03
Hello, I confirm that the bug is still present in LibO 5.0.1.2 on Win 7 x64. The behavior seems actually _worse_. For instance: CASE 1: bad behavior (bug) 1) create a new document 2) type www.example.com 3) press ENTER 4) => auto correct = the text is turned into a URL 5) press CTRL+Z 6) => the new line is removed but the text still is a URL 7) press CTRL+Z again 8) => nothing happens (document flickers slightly) (_that's new as far as I remember!_) 9) press CTRL+Z yet again 10) => the URL finally turns back into a text CASE 2: good behavior 1) create a new document 2) type www.example.com 3) press SPACE 4) => auto correct = the text is turned into a URL 5) press CTRL+Z 6) => the URL turns back into a text and the new space remains 7) press CTRL+Z again 8) => the space is removed
As suggested in comment #6, I just tested the bug on LibO 3.3.0.4 on Windows XP: - the bug is already here - what I described as probably new in CASE 1 part 8) is indeed not here So setting version to "inherited from OOo"
*** Bug 90645 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 44062 ***