Bug 139650 - Image going off page after DOCX export and deleting certain area (differs from ODT)
Summary: Image going off page after DOCX export and deleting certain area (differs fro...
Status: RESOLVED DUPLICATE of bug 138782
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.3.0.3 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisectRequest, regression
Depends on:
Blocks: DOCX-Anchor-and-Text-Wrap
  Show dependency treegraph
 
Reported: 2021-01-15 15:06 UTC by Telesto
Modified: 2021-07-16 10:50 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Example file (930.99 KB, application/vnd.oasis.opendocument.text)
2021-01-15 15:06 UTC, Telesto
Details
The example file and its docx version in Word (482.28 KB, image/png)
2021-07-16 10:07 UTC, NISZ LibreOffice Team
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Telesto 2021-01-15 15:06:43 UTC
Description:
Image going off page after DOCX export and deleting certain area (differs from ODT)

Steps to Reproduce:
1. Open the attached file
2. Save as DOCX
3. File reload
4. Select the yellow area
5. Hit backspace.

Actual Results:
One image going nearly full of page

Expected Results:
Compare ODT behavior


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 7.2.0.0.alpha0+ (x64)
Build ID: f2171af6ce3516598d9f8bac8294025a21a5b1a2
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 2021-01-15 15:06:56 UTC
Created attachment 168914 [details]
Example file
Comment 2 Telesto 2021-01-15 15:11:19 UTC
Also in
Version: 6.2.4.0.0+
Build ID: 5c5eab3522368d6baa7ab6ef1b6c9f5eaaab4fad
CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win; 
Locale: nl-NL (nl_NL); UI-Language: en-US
Calc: CL

and in
Versie: 5.3.5.2 
Build ID: 50d9bf2b0a79cdb85a3814b592608037a682059d
CPU-threads: 4; Besturingssysteem:Windows 6.2; UI-render: standaard; Layout Engine: new; 
Locale: nl-NL (nl_NL); Calc: CL


still within range of expectations (slightly different compared to ODT (but maybe different type of anchoring)
Versie: 5.1.6.2 
Build ID: 07ac168c60a517dba0f0d7bc7540f5afa45f0909
CPU Threads: 4; Versie besturingssysteem:Windows 6.2; UI Render: GL; 
Locale: nl-NL (nl_NL); Calc: CL
Comment 3 Telesto 2021-01-15 15:13:29 UTC
Adding NISZ because DOCX and this anchoring currently being a hot topic... will bibisect this myself eventually.. if not done before
Comment 4 Dieter 2021-05-17 15:44:23 UTC
I confirm it with

Version: 7.1.3.2 (x64) / LibreOffice Community
Build ID: 47f78053abe362b9384784d31a6e56f8511eb1c1
CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: en-GB
Calc: CL

Anchor in odt-file is left from first image; Anchor in docx-file is within the text and you can't place it left of the first image
Comment 5 NISZ LibreOffice Team 2021-07-16 10:07:56 UTC
Created attachment 173625 [details]
The example file and its docx version in Word

The image with the 3 people and the starry logo is a grouped shape which has the Contour wrap turned on.
You can see that text goes above and below the starry logo.
When exported to DOCX, the Contour wrap setting is lost and the text layout changes a bit. This is something still to fix.

However I can't reproduce the original problem anymore in:
Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: da13b76e07231131cb951868a314ee6f51c0f254
CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win
Locale: hu-HU (hu_HU); UI: en-US
Calc: CL

Now the deletion of the yellow part does not move the grouped shape off page.

Verified that this is so since:

https://git.libreoffice.org/core/commit/5812fb81013cc124a9b6a0b9912a34cc715fc495

tdf#138782 DOCX import: fix frame positions of old docs
Comment 6 NISZ LibreOffice Team 2021-07-16 10:08:23 UTC

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