Created attachment 169296 [details] A simple list with an empty element Attachment contains an input list field with two elements, second of which is empty. Saving it as DOCX makes the resulting file show an error at opening in Word 2016: > Word experienced an error trying to open the file. > Please try the following suggestions. Reproducible with current master, and also with LO 3.3 (OOo can't export to DOCX).
Created attachment 169297 [details] Image of window error message pop-up when opening .DOCX file
Reproduced by saving the file attached in the original bug report as a .DOCX file in Ubuntu 20.04.1 using Writer Version: 6.4.6.2 Build ID: 1:6.4.6-0ubuntu0.20.04.1 then opening the saved .DOCX file in Windows 10 using Writer Version 7.0.4.2 Build: dcf040e67528d9187c66b2379df5ea4407429775
Could you provide the exact steps you used to create the document please?
(In reply to Dave Potter from comment #3) > Could you provide the exact steps you used to create the document please? Definitely. 1. Receive a broken DOCX document from a user privately. 2. Start cleaning its XML to nail down the problem. 3. Find out that the field is the culprit, and that removing the empty item fixes the problem. 4. Save the original broken document to ODF, removing everything except the problematic field ;-P So no, I don't know how it was created initially. Maybe it was created elsewhere, e.g. in Word, and then re-saved in LibreOffice. The problem is that LibreOffice saves invalid XML (or at least unreadable by Word); LibreOffice could of course consider the empty entry invalid (and drop on import), or do something else :-D
Hi Mike I can reproduce the symptoms of the bug report by saving the attached odt file as a docx and trying to open it in microsoft word. What I can't do is reproduce the file that is attached. Writer will not allow me to add a completely empty input field in a list and if I add a field that has a space in it the problem does not reoccur. Have you any idea how this file was originally produced? If not, then I suggest that the bug should be closed as the underlying scenario cannot be reproduced.
(In reply to Dave Potter from comment #5) Unfortunately, this is not that simple. The problem arose in a real life. I can't find out the steps to repro the problematic document from scratch, but it doesn't mean that it should be closed. There might be some sequence in LO, or there might be some way to create that in other applications (that we don't control). The bugdoc file is a valid ODF, and thus if some (external?) entity is able to produce it, it is expected that LO does not misbehave when processing such files. If it has such input, and exports it to DOCX, it must produce a valid output.
Understood Mike and in principal I agree. However, what if the odt was generated in error by an old version of LO that had a bug in it that has now been corrected and hence the scenario will not reoccur. Or, does the bug need to be addressed from a legacy compatibility perspective regardless?
Dear Mike Kaganski, 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