Created attachment 68089 [details] Text with a frame anchored to a character If you insert a frame anchored to a character in a paragraph, the frame is eventually moved to the beginning of the paragraph if the paragraph also contains text deleted with "track/record changes" enabled. Steps to reproduce: Open an ODT document. Insert a frame anchored with a character in the middle of a paragraph. (The frame is to be displayed horizontally aligned with the character, for example in the margin.) Turn on track changes, "show changes" enabled. Delete some text in the paragraph containing the frame. Save the file or disable "show tracked changes" and re-enable it. The frame will move to the beginning if the paragraph. This is a very old bug, see OpenOffice bug list: bug 100682 (reported in 2009) https://issues.apache.org/ooo/show_bug.cgi?id=100682 bug 95810 (reported in 2008) https://issues.apache.org/ooo/show_bug.cgi?id=95810 (is probably the same bug, although "track changes" is not mentioned) Quote from OO bug list for #100682: First investigation reveals the following: - For saving, the delete track-changes are hidden. Afterwards they are shown again. This switch causes the described defect. - Switching the change tracking show mode off and on again causes the same defect. - Occurs since OOo 1.0
(In reply to comment #0) > Open an ODT document. > Insert a frame anchored with a character in the middle of a paragraph. (The > frame is to be displayed horizontally aligned with the character, for > example in the margin.) > Turn on track changes, "show changes" enabled. > Delete some text in the paragraph containing the frame. > Save the file or disable "show tracked changes" and re-enable it. > The frame will move to the beginning if the paragraph. Confirmed with: LO 4.0.2.2 Build ID: own W7 debug build Windows 7 Professional SP1 64 bit Just disabling and re-enabling "show tracked changes" didn't move the frame. Moved when file saved.
** 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 (4.4.1.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) Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-03-03
Still reproducible in LibreOffice 4.4.3.0.0+ built at home under Ubuntu 14.10 x86-64. Best regards. JBF
** 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.5 or 5.1.2 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: 2016-04-16
Still reproducible in LO 5.1.4.0.0+ and master, both build at home under Ubuntu 16.04 x86-64. As the anchor is changed when disabling and enabling the track change, it is a kind of data loss. Adding the keyword. Best regards. JBF
** 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.2.7 or 5.3.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-20170522
Still reproducible with LO 5.4.1.0.0+ built at home under Ubuntu 16.04 x86-64. Best regards. JBF
This no longer happens in 6.3. Bibisected using bibisect-win32-6.3 to: https://gerrit.libreoffice.org/plugins/gitiles/core/+/3345feb67f2c49a1b76639965b56968e1c5f03ee author Michael Stahl <Michael.Stahl@cib.de> Thu Jul 11 18:37:28 2019 +0200 committer Miklos Vajna <vmiklos@collabora.com> Mon Jul 22 14:14:06 2019 +0200 tdf#117185 tdf#110442 sw: bring harmony & peace to fly at-char selection Thanks Michael!