Bug 104260 - FILEOPEN DOCX: Images in table appear only once
Summary: FILEOPEN DOCX: Images in table appear only once
Status: RESOLVED FIXED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:docx
Depends on:
Blocks: DOCX-Tables
  Show dependency treegraph
 
Reported: 2016-11-29 15:55 UTC by Gabor Kelemen (allotropia)
Modified: 2022-06-30 22:16 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
The problematic file (40.87 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2016-11-29 15:55 UTC, Gabor Kelemen (allotropia)
Details
The document in Word 2010 (210.11 KB, image/png)
2016-11-29 15:56 UTC, Gabor Kelemen (allotropia)
Details
The document in 5.3 master (68.52 KB, image/png)
2016-11-29 15:56 UTC, Gabor Kelemen (allotropia)
Details
Screenshot of the document in current Writer master (114.93 KB, image/png)
2019-10-21 08:35 UTC, NISZ LibreOffice Team
Details
Screenshot of the document in more current Writer master (117.99 KB, image/png)
2019-10-21 09:11 UTC, NISZ LibreOffice Team
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Gabor Kelemen (allotropia) 2016-11-29 15:55:26 UTC
Created attachment 129129 [details]
The problematic file

Attached document is a template for business cards. 
It has 8 identical cards and each contain two images, one in the bottom left corner and one in the bottom right.

In Writer the one in the bottom right is visible, but all 8 of them are misplaced, they appear stacked on top of each other.
The ones in the bottom left appear in the Navigator, but not on the page.
Comment 1 Gabor Kelemen (allotropia) 2016-11-29 15:56:04 UTC
Created attachment 129130 [details]
The document in Word 2010
Comment 2 Gabor Kelemen (allotropia) 2016-11-29 15:56:30 UTC
Created attachment 129131 [details]
The document in 5.3 master
Comment 3 Telesto 2016-11-29 16:26:34 UTC
Confirming with:
Version: 5.4.0.0.alpha0+ (x64)
Build ID: 7aa2b5a041df8e71a435cccbc79ee13799ec9138
CPU Threads: 4; OS Version: Windows 6.19; UI Render: default; Layout Engine: new; 
TinderBox: Win-x86_64@62-TDF, Branch:MASTER, Time: 2016-11-24_11:40:27
Locale: nl-NL (nl_NL); Calc: CL

and with:
* Versie: 4.4.6.3 
Build ID: e8938fd3328e95dcf59dd64e7facd2c7d67c704d
Locale: nl_NL

* Version: 4.3.0.4
Build ID: 62ad5818884a2fc2e5780dd45466868d41009ec0
* Looking slightly better

*LibreOffice 3.3.0 
OOO330m19 (Build:6)
tag libreoffice-3.3.0.4
* Looking slightly better
Comment 4 QA Administrators 2018-03-11 03:41:05 UTC Comment hidden (obsolete)
Comment 5 Roman Kuznetsov 2018-11-26 14:56:11 UTC
still repro in 

Version: 6.2.0.0.beta1
Build ID: d1b41307be3f8c19fe6f1938cf056e7ff1eb1d18
CPU threads: 4; OS: Windows 6.1; UI render: default; VCL: win; 
Locale: ru-RU (ru_RU); UI-Language: en-US
Calc: threaded
Comment 6 NISZ LibreOffice Team 2019-10-21 08:35:00 UTC
Created attachment 155178 [details]
Screenshot of the document in current Writer master

Seems to have gotten better in 6.4.

Now the images are aligned in the correct row of the table, but not the correct column, so in each row two images are on top of each other in the corner of the right column.
Comment 7 NISZ LibreOffice Team 2019-10-21 09:11:36 UTC
Created attachment 155182 [details]
Screenshot of the document in more current Writer master

Correction, in 

Version: 6.4.0.0.alpha1+ (x86)
Build ID: f0340d58cc0f2808ce8003099ff2a0495360f267
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win; 
Locale: hu-HU (hu_HU); UI-Language: en-US
Calc: CL

even the column level alignment is correct now. 
This is a 5 days old nightly version, previous image was made with a 7 days old bibisect-win64-6.4
Comment 8 Xisco Faulí 2019-10-21 09:42:51 UTC
Issue fixed by https://cgit.freedesktop.org/libreoffice/core/commit/?id=e042a83843ed2573dbce9338058b3dc545dd6898

@NISZ LibreOffice Team, it would be wonderful if you could create a unittest for this issue...
Closing as RESOLVED FIXED