Description: I have a docx document generated from some web app. In previous version of writer 7.1 crashed when I opened the document (bug 140137 - resolved in version 7.2). Now it is OK to open it, but one of tables in document has a bad view (aganist view in MS Ofice). Maybe is a bug on web app which was generated the document, but why MS Word open it correctly?. There is probably problem with merged cells on rows from 6 to 11. In these rows it should be merged columns from 1 to 11 and the last column should be separately. Like in the view in MS Word 2019. Screenshots of bad view od table in Writer and correct view of table in MS Word 2019 are in attachments. Steps to Reproduce: 1. Open the document 2. Go to the page 8 3. See the table Actual Results: Bad view of the table Expected Results: Correct view of table Reproducible: Always User Profile Reset: No Additional Info: Correct view of table
Created attachment 170247 [details] web app generated docx document with table
Created attachment 170248 [details] Bad view of table in writer
Created attachment 170249 [details] Correct view in MS Word 2019
Repro with Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 722ec600e85cca2e94e82e69f8d13773061172b9 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: nl-NL Calc: CL File doesn't open with Versie: 6.0.4.1 Build ID: a63363f6506b8bdc5222481ce79ef33b2d13c741 CPU-threads: 4; Besturingssysteem: Windows 6.3; UI-render: GL; Locale: nl-NL (nl_NL); Calc: CL
Created attachment 170265 [details] Trimmed down version
Also in Versie: 4.1.0.4 Build ID: 89ea49ddacd9aa532507cbf852f2bb22b1ace28 Broken differently in 4.0 Adding bibisectrequest to figure out who and how the - overall - improvement change is made
Created attachment 170270 [details] Trimmed down version resaved in MSO as compatible Original attachment 170247 [details] is 19 pages in MSO. Trouble table is page 8. Trimmed down (wasn't explain how but seems correctly) attachment 170265 [details] is 3 pages, same table at page 3. Lo opens 2 pages, no table. Opening in LO 7.2+ gives error: SAXException: [word/document.xml line 1]: unknown error Further: File format error found at [mscx_uno bridge error] UNO type of C++ exception unknown: "o3tl.divide_by_zero", RTTI-name=".?AUdivide_by_zero@o3tl@@"! SAXParseException: '[word/document.xml line 1]: unknown error', Stream 'word/document.xml', Line 1, Column 30667(row,col). Document.xml sholdn't have Line 1, Column 30667 but is in UTF-8-BOM, instead of UTF-8. So I don't know how bad table could be seen. Note: We have few bugs with generated content (always search before submitting) where they are usually not fully in standard, but MSO still reads them. Important: If document is resaved in MSO, both compatible or new, LO opens it properly. Here I attach compatible one from MSO.
My 7.2+ wasn't fresh, when I updated it I reproduced as reported.
Original attachment 170247 [details] is 19 pages in MSO. Trouble table is page 8. Trimmed down (wasn't explain how but seems correctly) attachment 170265 [details] is 3 pages, same table at page 3. Lo opens 2 pages, no table. Note: We have few bugs with generated content (always search before submitting) where they are usually not fully in standard, but MSO still reads them. If document is resaved in MSO, both compatible or new, LO opens it properly. Here I attached compatible one from MSO as attachment 170270 [details]. I bibisected improvement in 41 and got "Drop redundant typedef" by S. Bergmann. So that's of no help.
Original document claims to be from <Application>Microsoft Office Word</Application> and 2007. Reduced version is from <ap:Application>Microsoft Word for the web</ap:Application> and 2016.
Dear Jan Chroust, 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