Created attachment 166451 [details] Sample DOCX Open the attached DOCX with a table in Writer. => The long cell that has "Test" in it is moved to the next page. The issue seems to depend both on the Heading line in the cell and the length of the cell. If the heading is removed or the table gets shorter, the table remains in one piece. Observed in LO 7.1.0.0.alpha0+ (f21f3d094cfb495c89dfb0a23ecb061ef1a2178e), 4.4.0.3 / Ubuntu. Fine in 3.6.0.4. => regression Bibisected to the following range using repo bibisect-43all. https://cgit.freedesktop.org/libreoffice/core/log/?qt=range&q=179a6db61ee30cf776747802f06edeef45fec461..5f91f8a368343d8921a01edb7359cd300892f09d
Created attachment 166452 [details] Screenshot in Writer
Created attachment 166453 [details] PDF exported from Word
Created attachment 166568 [details] Sample compared in MSO and LO as 2007 DOCX, new DOCX, DOC Not a straightforward bug. While report is literally true, this is 2007 DOCX. If resaved and reeopen in MSO, it's different, like in LO. I usually close such bugs as "NotOurBug" with the explanation that it's not realistic for LO to emulate different MSO behavior.
Created attachment 166569 [details] Sample DOCX 2007 resaved in MSO as new DOCX
Created attachment 166570 [details] Sample DOCX 2007 resaved in MSO as DOC I'd rather convert this bug to DOC because LO should open it as MSO.
(The term "heading" is a bit misleading since the table doesn't have any "header rows". So it is a "human" heading only.) Technically this is a Word 2010 format document. If Word 2016 resaves it "in compatibility mode" then it continues (in Word) to split the tall row. When Word 2016 saves it in native compat15 mode, then the full-of-content-cell moves to the next page. Starting in LO 7.0, we now export DOCX as compat15 mode - so anything LO authors should look proper in non-obsolete MS Word. This is strictly a layout issue. If we add in the support for DOC, we might as well add in support for compat14 DOCX as well. The question is whether it is worth the effort to add more complexity to the layout - and what other side issues this would trigger. [At this point, I would consider it a WONTFIX, at least as a volunteer.] See related bug 123116 and bug 105478 for code pointers (and warnings).
Dear Aron Budea, 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