Bug 136581 - Page frame moves to different position after anchor change and save to DOCX (save & reload)
Summary: Page frame moves to different position after anchor change and save to DOCX (...
Status: RESOLVED DUPLICATE of bug 37002
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.2.0.4 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisectRequest
Depends on:
Blocks:
 
Reported: 2020-09-08 19:00 UTC by Telesto
Modified: 2024-02-28 03:29 UTC (History)
0 users

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Telesto 2020-09-08 19:00:56 UTC 
Description:
Page frame moves to different position after anchor change and save to DOCX (save & reload)

Steps to Reproduce:
1. Open the attached file
2. Save as DOCX
3. Select the frame 
4. Right click -> anchor to page
5. Save 
6. Reload

Actual Results:
Frame moves down after reload

Expected Results:
Same position as on screen


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 7.1.0.0.alpha0+ (x64)
Build ID: e8b8e7be0b2ad693224cd94062a55610eb69df7e
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
Comment 1 Telesto 2020-09-08 19:01:57 UTC 
Also in
Versie: 4.4.7.2 
Build ID: f3153a8b245191196a4b6b9abd1d0da16eead600
Locale: nl_NL
Comment 2 Telesto 2020-09-08 19:04:31 UTC 
Versie: 4.2.0.4 
Build ID: 05dceb5d363845f2cf968344d7adab8dcfb2ba71
Comment 3 Telesto 2020-09-08 19:07:17 UTC 
Didn't work in (and older)
Versie: 4.1.0.4 
Build ID: 89ea49ddacd9aa532507cbf852f2bb22b1ace28

Adding bibisectrequest, as this might be an implementation error
Comment 4 Telesto 2020-09-09 09:55:51 UTC 
Bit pointless.. Anchor to page & not supported with DOCX. Moves Anchor out header to page
Comment 5 Stéphane Guillou (stragu) 2024-02-28 03:29:04 UTC 

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