Tested with LibreOffice 3.4.2 OOO340m1 (Build:203) on Linux How to reproduce: 1. create an empty text document in writer 2. disable "Edit->Changes->Record" 3. disable "Edit->Changes->Show" 4. enable "View->Toolbars->Bullets and Numbering" 5. Type a paragraph, e.g. "the quick brown flying fox jumped over the lazy dog" 6. Start a new paragraph hitting enter key 7. Type another paragraph, e.g. "Franz jagt im komplett verwahrlosten Taxi quer durch Bayern" 8. enable "Edit->Changes->Record" 9. enable "Edit->Changes->Show" 10. Move the cursor into the first line, delete some text, e.g. the word "flying " - leave the cursor in that line 11. Use "ctrl-alt-cursor-down" (equivalent to the single down arrow of the Bullets and Numbering toolbar) to move the first paragraph down under the second paragraph 12. Since Record & Show Changes is enabled the first paragraph gets crossed out (as expected) 13. the text is moved down (as expected) but 14. ups, the deleted text is back in this moved paragraph, so I get "the quick brown flying fox jumped over the lazy dog" and need to correct it again.... In step 14 I expected either 1. the 1st paragraph including the deleted text still marked as deleted text; or 2. the 1st paragraph but the previously deleted text "flying " being completely forgotten - since in terms of the Record Changes logic I guess this is all new text at its new position except for the previously deleted text. If I "simulate" the "ctrl-alt-cursor-down" function by the sequence of marking the complete 1st paragraph, ctlr-x it and move the cursor down under the last paragraph and ctrl-v it I get the second option of what I expected. On a side note this seems to be connected to Bug 38745 since I also get that crash when messing with the undo/redo function afterwards.
[This is an automated message.] This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it started right out as NEW without ever being explicitly confirmed. The bug is changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases. Details on how to test the 3.5.0 beta1 can be found at: http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1 more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
reproduced in LibO 3.6.0 master on Fedora 64 bit
Just reproduced in LO Version 3.6.5.2 (Build ID: 5b93205).
Testing sth. else, this is still a problem in 4.0.5.
This is still a problem in LO 4.3.2. on Win64.
** 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.1 or preferably 5.0.2.2 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-10-14
Same behavior in 5.1+.
** 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.1.6 or 5.2.3 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 helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20161108
Still the same behavior in LibreOffice 5.2.3.2 on Xubuntu LTR 16.04.1.
** 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 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
Still the same behaviour on Version: 6.0.4.2 Build-ID: 9b0d9b32d5dcda91d2f1a96dc04c645c450872bf CPU-Threads: 4; BS: Linux 4.4; UI-Render: Standard; VCL: gtk2; Gebietsschema: de-DE (de_DE.UTF-8); Calc: group
Still reproducable on LODev daily build: Version: 6.2.2.0.0+ Build-ID: ba5e640cc4880ef023b5ea501b1b99e0a3ba25bd CPU-Threads: 4; BS: Linux 4.4; UI-Render: Standard; VCL: gtk3; TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:libreoffice-6-2, Time: 2019-02-13_04:26:01 Gebietsschema: de-DE (de_DE.UTF-8); UI-Sprache: de-DE Calc: CL
It seems, this ugly bug was solved during the sw_redlinehide development.
Created attachment 166793 [details] Simplified example file to demonstrate the problem
Created attachment 166794 [details] The example file in current Writer This file has two lists of two bulleted paragraphs, separated by an empty one. One word is deleted from all lines. Moving them will have some funny side effects... Version: 7.1.0.0.alpha1+ (x64) Build ID: f27c4ec5c864395f4cdaec32d7e95ff24e4f43c8 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win Locale: hu-HU (hu_HU); UI: en-US Calc: CL
Created attachment 166795 [details] The example file after moving the first paragraphs down Moving down the first paragraph in the first bulleted list makes the deleted word accepted (and the empty line appears as changed), while in the second bulleted list it makes the deleted word rejected.
Created attachment 166796 [details] The example file after moving the first sentences down
Back to NEW.
László Németh committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/b5ab4836c03e9428aff6a48843f2a054ceff0f85 tdf#39721 sw change tracking: fix move down It will be available in 7.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Verified in Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 44b914b1e2616ca8f70e896e653a46ca93610234 CPU threads: 4; OS: Windows 10.0 Build 17134; UI render: Skia/Raster; VCL: win Locale: hu-HU (hu_HU); UI: hu-HU Calc: threaded