Created attachment 177272 [details] contourWrapSplittingTable.docx: after LO round-trip, becomes several pages long in MS Word. This problem is only seen in MS Word (tested 2003/2010/2016). After this one-page document is round-tripped by LO, it opens in MS Word as a 6 pager, where each table row is on a separate page. In LO (and in Word before a RT) it all fits on one page. [I don't have the original Word document, so I edited the contents by hand to create this example. When I tried to anonymize the contents with search/replace in Word 2016, then that version of the document round-tripped just fine.] This is somehow connected to the contour wrapping on the header logo, and the table width. If contour wrapping is turned off, then the table doesn't split. Alternatively, if the table is shortened so that it doesn't interact with the logo (to something like 20 cm), then the table doesn't split. So this seems like a quirk in Word more than anything else. (Notice that the round-tripped DOCX is fine in Word 2003, but not in 2010/2016.) The same problem happens if round-tripped to .DOC format - and surprisingly Word 2003 also splits the table this time around. I'm only documenting this as an example of a goofy Word issue. I didn't see any one thing specifically wrong with LO export. It just seems like a certain combination of factors results in this odd layout in Word. No bibisect needed. It didn't happen in earlier versions which didn't have the ability to handle contour wrapping.
Justin, I'm sorry but I don't know what to do to reproduce the bug. If I open attachment with Word2016 everything is fine. So please add some clearer steps to reproduce. Thank you. => NEEDINFO
1.) Open contourWrapSplittingTable.docx in LO. 2.) resave it. 3.) Open the resaved file in MS Word.
I confirm it with Version: 7.2.5.2 (x64) / LibreOffice Community Build ID: 499f9727c189e6ef3471021d6132d4c694f357e5 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL and Word 2016
Dear Justin L, 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