Bug 82064 - FILEOPEN: DOCX Strict missing last page with 2 frames
Summary: FILEOPEN: DOCX Strict missing last page with 2 frames
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.2.5.2 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: dataLoss, filter:docx
Depends on:
Blocks: OOXML-Import-Strict OOXML-Shapes
  Show dependency treegraph
 
Reported: 2014-08-02 22:32 UTC by Yousuf Philips (jay) (retired)
Modified: 2025-05-23 03:13 UTC (History)
6 users (show)

See Also:
Crash report or crash signature:


Attachments
Last page in Word 2013 vs LibO 4.3.1 (216.78 KB, image/png)
2014-08-02 22:32 UTC, Yousuf Philips (jay) (retired)
Details
Reduced test document, nothing is visible (111.72 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2014-08-03 13:55 UTC, Jorendc
Details
How reduced test file should look like (42.87 KB, image/png)
2014-08-03 13:56 UTC, Jorendc
Details
trimmed sample (111.32 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2017-10-23 06:18 UTC, Yousuf Philips (jay) (retired)
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Yousuf Philips (jay) (retired) 2014-08-02 22:32:31 UTC
Created attachment 103875 [details]
Last page in Word 2013 vs LibO 4.3.1

Steps:
1) Open attachment 103836 [details]
2) Scroll down to last page
3) last page doesnt have 2 frames in it

Tested on LibO 4.2.5 and 4.3.1 on Linux Mint.
Comment 1 Jorendc 2014-08-03 13:55:15 UTC
Created attachment 103907 [details]
Reduced test document, nothing is visible
Comment 2 Jorendc 2014-08-03 13:56:26 UTC
Created attachment 103908 [details]
How reduced test file should look like
Comment 3 Jorendc 2014-08-03 13:56:56 UTC
Repro, windows 8.1 with LibreOffice Version: 4.4.0.0.alpha0+
Build ID: 6528607d34c9a2098ff5eec051fc9299ec37dfd7
TinderBox: Win-x86@39, Branch:master, Time: 2014-08-03_07:56:26
Comment 4 QA Administrators 2015-10-14 19:58:00 UTC Comment hidden (obsolete)
Comment 5 Andrey Skvortsov 2015-11-26 11:23:28 UTC
The problem is still exist. Tested on LO 5.0.3.2 (Linux amd64 and Windows 7 amd64).
Clean installation of Word 2010 shows empty page as LibreOffice does. But after recommended installation of Microsoft's 'OOXML strict converter for Office 2010' all is correct. 

I want to point, that text in the document, that is not shown, is written inside of floating Text Box (from insert/shape menu in Word). I had many issues with these Word's 'drawing tools'.
Comment 6 Robinson Tryon (qubit) 2015-12-10 01:33:11 UTC Comment hidden (obsolete)
Comment 7 QA Administrators 2017-01-03 19:42:51 UTC Comment hidden (obsolete)
Comment 8 vihsa 2017-06-01 10:57:11 UTC
reproducible
Version: 5.5.0.0.alpha0+
Build ID: ec79f3453471ee9b6ae32e71ff16ea99d9b7751c
TinderBox: Android-ARM@24-Bytemark-Hosting, Branch: master, Time: 2017-05-28 22:44:13
Comment 9 vihsa 2017-08-30 12:51:23 UTC
docx file display blank document

5.0.0.0.alpha1+ [ build id: ab465b9 ]
5.1.0.0.alpha1+ [ build id: 1a6ec13 ]
5.1.0.0.alpha1+ [ build id: 5b791ec ]
5.2.0.0.alpha0+ [ build id: f6a74ce ]
5.3.0.0.alpha1+ [ build id: 4136757 ]
5.4.0.0.alpha0+ [ build id: 3902bb7 ]

os: android 5.1
device: lyf flame 3 [ ls-4001 ]
Comment 10 Yousuf Philips (jay) (retired) 2017-08-31 09:59:29 UTC
If i compare the transitional and strict xml, transitional has xml like this for the 2 frames

<w:r>
  <w:rPr>
  <mc:AlternateContent>
    <mc:Choice Requires="wps">
      <w:drawing>
    </mc:Choice>
    <mc:Fallback xmlns:w15="...">
      <w:pict>
    </mc:Fallback>
  </mc:AlternateContent>
</w:r>

while strict only has these

<w:r>
  <w:rPr>
  <w:drawing>
</w:r>

and after a bit of digging, i think that LO does support the <wp:wsp> tag found under the <w:drawing> tag, like so, as it does support the <pic:pic> tag when its in its place.

<w:drawing>
 <wp:anchor ...>
   <a:graphic ...>
     <a:graphicData ...>
       <wp:wsp>
         <wp:cNvSpPr ...>
         <wp:spPr ...>
         <wp:txbx>
         <wp:bodyPr ...>
       </wp:wsp>
     </a:graphicData>
   </a:graphic>
 </wp:anchor>
</w:drawing>

@Justin, @Mike, @Miklos: Any thoughts?
Comment 11 Yousuf Philips (jay) (retired) 2017-10-23 06:18:39 UTC
Created attachment 137224 [details]
trimmed sample
Comment 12 QA Administrators 2018-10-24 02:57:07 UTC Comment hidden (obsolete, spam)
Comment 13 Timur 2020-01-09 17:27:56 UTC Comment hidden (obsolete)
Comment 14 QA Administrators 2022-07-26 03:29:33 UTC Comment hidden (obsolete)
Comment 15 Timur 2022-07-26 09:05:36 UTC
Repro 7.5+
Comment 16 QA Administrators 2025-05-23 03:13:02 UTC
Dear Yousuf Philips (jay) (retired),

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

MassPing-UntouchedBug