Bug 144568 - To character anchor of image frame becomes 'to paragraph' anchor on DOCX export (OK with DOC)
Summary: To character anchor of image frame becomes 'to paragraph' anchor on DOCX expo...
Status: RESOLVED DUPLICATE of bug 143591
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.3.0.4 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-09-17 08:43 UTC by Telesto
Modified: 2021-09-21 09:24 UTC (History)
1 user (show)

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 2021-09-17 08:43:31 UTC 
Description:
To character anchor of image frame becomes 'to paragraph' anchor on DOCX export (OK with DOC)

Steps to Reproduce:
1. Open attachment 164569 [details]
2. Export to DOCX
3. File reload -> Right click the frame -> Notice anchor to be 'to paragraph'

Actual Results:
To paragraph anchor

Expected Results:
To character


Reproducible: Always


User Profile Reset: No



Additional Info:
Found in
Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: d5e55d204b71710eb5eb5d2c683dd6698626df3c
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

and in
Versie: 4.4.7.2 
Build ID: f3153a8b245191196a4b6b9abd1d0da16eead600
Locale: nl_NL

and in
Version: 4.3.7.2
Build ID: 8a35821d8636a03b8bf4e15b48f59794652c68ba

not in
Versie: 4.2.0.4 
Build ID: 05dceb5d363845f2cf968344d7adab8dcfb2ba71
Comment 1 Telesto 2021-09-17 08:44:08 UTC 
Likely an implementation error..
Comment 2 NISZ LibreOffice Team 2021-09-21 08:56:48 UTC 
Isn't this the same case as bug 143591 ?
Comment 3 Telesto 2021-09-21 09:21:18 UTC 

*** This bug has been marked as a duplicate of bug 143591 ***
Comment 4 Telesto 2021-09-21 09:24:43 UTC 
(In reply to NISZ LibreOffice Team from comment #2)
> Isn't this the same case as bug 143591 ?
Ouch, yes.. My memory pretty unreliable & forgot search..