Created attachment 117374 [details] XLS Files row Height difference Attached XLS file shows almost collapsed rows in all LIBO versions, as the row height set to those rows are very small. But all the rows are visible in Excel and OpenOffice. I digged in further and saved the xls file as ods, both through LibreOffice and OpenOffice and analyzed the difference in the xml. LIBREOFFICE Behaviour:- The row height in 'ro2' is very small and also use-optimal-row-height is set as false. Hence LibreOffice UI displays the rows with the same small height(which almost looks like collapsed rows.). <style:style style:name="ro1" style:family="table-row"> <style:table-row-properties style:row-height="14.66pt" fo:break-before="auto" style:use-optimal-row-height="false"/> </style:style> <style:style style:name="ro2" style:family="table-row"> <style:table-row-properties style:row-height="0.74pt" fo:break-beforeauto="" style:use-optimal-row-height="false"/> </style:style> <style:style style:name="ro3" style:family="table-row"> <style:table-row-properties style:row-height="12.81pt" fo:break-beforeauto="" style:use-optimal-row-height="false"/> </style:style> OpenOffice Behaviour:- Though the row height of 'ro2' is very small in this case also, use-optimal-row-height is set as true. Hence, when the file is opened in any UI the row heights get recalculated according to the content and all the rows are visible just like the original xls file. <style:style style:name="ro1" style:family="table-row"> <style:table-row-properties style:row-height="0.1665in" fo:break-beforeauto="" style:use-optimal-row-height="true"/> </style:style> <style:style style:name="ro2" style:family="table-row"> <style:table-row-properties style:row-height="0.0102in" fo:break-beforeauto="" style:use-optimal-row-height="true"/> </style:style> <style:style style:name="ro3" style:family="table-row"> <style:table-row-properties style:row-height="0.178in" fo:break-beforeauto="" style:use-optimal-row-height="true"/> </style:style> File attached, was created in EXCEL.
What were the versions of LibO and AOO that you saved the .ods files with? Or did you test against the older OOo?
I tried on version 4.3.3.4. Even the recent version's behaviour is same.
I take it you meant 4.3.3.2, so setting the version field to it (must be earliest affected).
Hello, is it duplicate of bug 62268?
Is it possible to reproduce this issue with .xlsx? If yes please attach .xlsx example.
It will be great also to attach .ods file, to check if it is an export to .xls/.xlsx issue.
Issue is not reproducible with xlsx or ods. Is is with xls alone.
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.4.1 or 5.3.6 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170929
I am moving this out of "critical". Critical is reserved for our most serious bugs, this is not one of those (no data loss, no crashes). Setting as: Normal: could in theory impact real world work
Dear Sugam, 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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear Sugam, 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
Reproduced in libreoffice-3.3.0, not in OOo 3.3. Office.com opens the file with all text visible. Unsure if it can be called a regression, but marking as "notBibsectable" anyway.