Bug 146384

Summary:	Undo of anchor change to as character doesn't restore image position for DOCX
Product:	LibreOffice	Reporter:	Telesto <telesto>
Component:	Writer	Assignee:	Not Assigned <libreoffice-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	nnamani.ezinne
Priority:	medium
Version:	7.2.1.2 release
Hardware:	All
OS:	All
See Also:	https://bugs.documentfoundation.org/show_bug.cgi?id=146383
Whiteboard:
Crash report or crash signature:		Regression By:

Description Telesto 2021-12-23 09:39:51 UTC

Description:
Undo of anchor change to character doesn't restore image position in DOCX

Steps to Reproduce:
1. Open attachment 164051 [details]
2. Save to DOCX
3. File reload -> Layout is not OK with master. See bug 146383
4. Change anchor for frame 1 to 'to character'
5. Press CTRL+Z

Actual Results:
Frame on different position

Expected Results:
Exactly as before


Reproducible: Always


User Profile Reset: No



Additional Info:
Found in
7.4

and in
Version: 7.2.1.0.0+ (x64) / LibreOffice Community
Build ID: 8fdbb8aed1b48734a717d5f98ada566de7204605
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

crash with
Version: 7.1.0.0.beta1+ (x64)
Build ID: f9fab4203c1aa0b9a3f27ce2713b6d5addc7df19
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

fine with
7.0b1

Comment 1 Ezinne 2021-12-28 10:15:22 UTC

At step 4, I see that frame 1 was already set to "To Character".

Please, retest the issue and update the steps.

Version: 7.4.0.0.alpha0+ / LibreOffice Community
Build ID: d272bf4f8f3a083b8c37f7b10f89cd2bf76b7d21
CPU threads: 8; OS: Linux 5.11; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded

Comment 2 Telesto 2021-12-28 12:10:08 UTC

1. Open attachment 164051 [details]
2. Save to DOCX
3. File reload -> Layout is not OK with master. See bug 146383
4. Change anchor for frame 1 to 'AS character'
5. Press CTRL+Z

Comment 3 Telesto 2021-12-28 12:57:46 UTC


*** This bug has been marked as a duplicate of bug 90858 ***