Bug 92444 - FILEOPEN: Frames overlapping in DOCX (see Comment 10)
Summary: FILEOPEN: Frames overlapping in DOCX (see Comment 10)
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected) Master
Hardware: All All
: medium normal
Assignee: Not Assigned
Keywords: filter:docx
Depends on:
Blocks: DOCX-Textbox
  Show dependency treegraph
Reported: 2015-06-30 08:20 UTC by mal
Modified: 2024-05-16 03:16 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:

docx that looks really bad (569.64 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2015-06-30 08:20 UTC, mal
Another example of frames overlapping (38.60 KB, application/vnd.ms-word.document.12)
2016-05-28 13:57 UTC, Buovjaga
docx that looks really bad looks OK when resaved in MSO 2016 (446.60 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2018-12-10 10:51 UTC, Timur
docx that looks really bad compared in LO 6.3+ MSO 2016 (194.57 KB, image/jpeg)
2018-12-10 10:52 UTC, Timur

Note You need to log in before you can comment on or make changes to this bug.
Description mal 2015-06-30 08:20:11 UTC
Created attachment 116944 [details]
docx that looks really bad

It was suggested that doc and docx documents that LO munges should  be reported as bugs.

If this is wrong please let me know who would be interested in these documents as we have quite a few. If this is the correct way to bring compatibility errors to light then I have a whole bunch of them you can look at.

The attached document is one a student brought in this morning.
It looks REALLY bad in 4.4.3 and just very bad in ( and
looks fine in Word 2013 surprisingly )

4.4.3 from openSUSE repos from Libreoffice
openSUSE 13.3 64bit 
Nvidia blob
KDE Plasma5

Comment 1 Marc Kaulisch 2015-06-30 08:38:59 UTC
Hello mal,
Thank you for reporting the bug. I can confirm that the bug is present in LO 64bit on Win8.1.

It is also a loss of information as the second page is not displayed.
Comment 2 mal 2015-06-30 08:53:03 UTC Comment hidden (no-value)
Comment 3 steve 2015-06-30 09:58:04 UTC
@mal: rule of thumb: one problem per bug. Otherwise things escalate quickly and it get's really hard to keep track of anything at all.

If you have a document which has 6 problems, open 6 reports. Interlinking the reports via the "see also:" field might be a good idea then.

But generally speaking: if you run into trouble it's always good to report the problem. That's the first step to improve the situation. QA will then deal with your reports i.e. mark them duplicates or valid + new etc.

As for filing good bug reports, this Wiki is a good starting point: https://wiki.documentfoundation.org/QA/BugReport

"looking bad" is not a good description. The more specific you can be the better. And giving good reproduce steps and clearly indicating what QA / devs should be looking for in the title of your bug + the description will help a lot to move things forward faster.
Comment 4 raal 2015-11-02 07:23:20 UTC Comment hidden (obsolete)
Comment 5 Timur 2016-02-23 10:01:41 UTC
Problem here is the opening of DOCX with frames. 
Opening was never fine, but it's better now from LO 5.0. At least you see it's not OK, unlike when you see 3 frames and don't know about other 3.
Comment 6 Buovjaga 2016-05-28 13:57:18 UTC
Created attachment 125350 [details]
Another example of frames overlapping

Looks like I don't have to create a new report :)
I thought I'd nevertheless upload this example DOCX coming from Word 2013.

Confirmed with Version:
Build ID: 9d2f7be4e65595241db3cf5135b69bd9e4ce6a30
CPU Threads: 4; OS Version: Windows 6.29; UI Render: default; 
TinderBox: Win-x86@42, Branch:master, Time: 2016-05-27_22:55:26
Locale: fi-FI (fi_FI)
Comment 7 QA Administrators 2017-12-08 08:05:49 UTC Comment hidden (obsolete)
Comment 8 Timur 2017-12-08 08:28:28 UTC Comment hidden (obsolete)
Comment 9 QA Administrators 2018-12-09 03:40:50 UTC Comment hidden (obsolete)
Comment 10 Timur 2018-12-10 10:47:31 UTC
Repro in LO 6.3+ with attachment 116944 [details]. Wee see 3 out of 6 frames. But that DOCX was created in Macintosh Word 2011. Opens OK in LO if resaved in MSO 2016. Yet we should open it properly. 

Attachment 125350 [details] is created in Microsoft Office Word 2013. With LO 6.3+ still shows the same overlap. That one is more appropriate for this bug.
Comment 11 Timur 2018-12-10 10:51:07 UTC
Created attachment 147413 [details]
docx that looks really bad looks OK when resaved in MSO 2016
Comment 12 Timur 2018-12-10 10:52:22 UTC
Created attachment 147414 [details]
docx that looks really bad compared in LO 6.3+ MSO 2016
Comment 13 NISZ LibreOffice Team 2020-05-15 07:25:15 UTC
(In reply to Timur from comment #11)
> Created attachment 147413 [details]
> docx that looks really bad looks OK when resaved in MSO 2016

This started to regress, opened bug #133054

Original is/was unchanged.
Comment 14 NISZ LibreOffice Team 2020-05-15 07:25:51 UTC
Also these are text boxes not frames, changing meta.
Comment 15 QA Administrators 2022-05-16 03:35:09 UTC Comment hidden (obsolete, spam)
Comment 16 QA Administrators 2024-05-16 03:16:32 UTC
Dear mal,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)

If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword

Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team