Description: Changing anchor from 'as character' to 'to character' splits frame and content and undo puts text above Steps to Reproduce: 1. open the attached file 2. Save as DOCX 3. File reload 4. Change the anchor to the frame to 'to character' 5. Press undo Actual Results: Frame and content splits at 'to character' and undo causes text below to move up Expected Results: Same as ODT Reproducible: Always User Profile Reset: No Additional Info: Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 93115d2c54d645bcf2f80fde325e3ede39dee4d5 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL
Created attachment 176061 [details] Example file
I confirm it with Version: 7.3.0.0.alpha1+ (x64) / LibreOffice Community Build ID: 7b8f630db30ee0066a9f4b6e540368d2fcad7fa8 CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL Steps to Reproduce: 1. open the attached file 2. Select Frame -> Anchor is "to character" and placed at the first character 2. Save as DOCX -> Select Frame -> Anchor is "to character" and placed at the first character 3. File reload 4. select frame -> Anchor is "to character", but is now at end of the paragraph 5. Select "to character" again => Anchor is moving 6. Press undo So I think main difference is, that there is something with the anchor after saving as docx. Very similar to bug 135155
*** Bug 149814 has been marked as a duplicate of this bug. ***
Let's reduce the bug to split of frame and content. Problem with undo should be a separate bug and it might have been reported in bug 135383 => I've changed bug summary Biug is still present in Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community Build ID: ce29e6299932fc079b05b60662ba95c8342990bc CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL
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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug