Description: When this document with this special frame created in MO is opened in LO the frame is lost, and as it is aligned to the right then the alignment is lost too. When the document is saved as doc with MO, the frame is not removed in LO. Steps to Reproduce: Open document in MO to verify frame exist Open document in LO to verify frame is removed Actual Results: The frame is removed Expected Results: The frame and its settings remain the same Reproducible: Always User Profile Reset: No Additional Info: Tested in 6.7.4.2 and in 7.0.4.2 LO versions CPU threads: 12; OS: Mac OS X 10.15.7; UI render: default; VCL: osx; Locale: en-US (en_CO.UTF-8); UI-Language: en-US Calc: threaded
Created attachment 169199 [details] Frame exists in MO
Created attachment 169200 [details] Frame is lost in LO
Created attachment 169201 [details] Docx to test
Created attachment 169202 [details] Doc with non-removed frame
Created attachment 169203 [details] Doc with non-removed frame
Updated steps to reproduce this issue Microsoft Word on version 16.45 = Issues Microsoft Word on version 15.32 = No issues - Create a Word document using Office 2016 on a MAC 16.45 or higher - Type some text - Click on Insert - Click Header > Select the first option - Click on Page Number > Page Number > Alignment - Right
No repro in Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 67f2a99229101757af4f40118f4d3c83ba38648b CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: en-US (ru_RU); UI: en-US Calc: threaded
Hello, can you clarify that the problem is in alignment of Page number fields? In Word are
Confirm with Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: 36efb384a66b6dd645e0ae80fd7df68370a9dc8b CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded and Version 4.1.0.0.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a) Frames (fields) are aligned left on the page, should be right.
Created attachment 174131 [details] field settings in word
*** This bug has been marked as a duplicate of bug 124481 ***