If I make a row with custom height with not cells in it and then save to xlsx format the information about row height is not in resulting worksheet xml file for the worksheet (contained in xlsx).
Reading empty rows from xlsx with custom height (written with MS Office) works OK.
Confirmed in 184.108.40.206 (Windows)
** 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 (4.3.5 or later): 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)
Thank you for your help!
-- The LibreOffice QA Team
The latest stable libreoffice in Gentoo is 220.127.116.11 so I can't retest it properly
Height of empty rows is now saved in .xlsx, changing to WFM.
Win 7 Pro 64-bit Version: 18.104.22.168.alpha0+
Build ID: 784d069cc1d9f1d6e6a4e543a278376ab483d1eb
TinderBox: Win-x86@62-TDF, Branch:MASTER, Time: 2015-01-25_23:07:36
*** Bug 99321 has been marked as a duplicate of this bug. ***
This bug was already fixed in LibreOffice 5.2
(In reply to Bartosz Kosiorek from comment #6)
> This bug was already fixed in LibreOffice 5.2
Is it the fix for bug 98106? You can close this as duplicate of 98106, if yes.