Bug 127442 - Auto row height not set / not remembered in Calc
Summary: Auto row height not set / not remembered in Calc
Status: RESOLVED DUPLICATE of bug 123034
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.3.1.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Regressions-row-height
  Show dependency treegraph
 
Reported: 2019-09-08 20:36 UTC by Nadie Nada Nunca
Modified: 2019-09-17 13:44 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nadie Nada Nunca 2019-09-08 20:36:36 UTC
Description:
Selecting the whole worksheet or a bunch of rows and double clicking on the cell indicator border doesn't set auto row height for the selected rows, nor does it invoking the "Optimal row height" menu, either by increasing the value or unticking the "Default value" checkbox. 

After manually setting auto height for the desired rows, saving the file and reopening again has the effect that all rows have a standard height again. The auto height setting is not remembered.

Steps to Reproduce:
1. Create a worksheet with some cells that are several lines high. 
2. Try to set auto height for all or several rows. (It fails.) 
3. Manually set auto height for the rows that need it. 
4. Save and reopen the file.

Actual Results:
Auto height setting is ignored on file open.

Expected Results:
Setting should be applied to all selected rows and remembered after saving the file.


Reproducible: Always


User Profile Reset: No



Additional Info:
Comment 1 Oliver Brinzing 2019-09-09 17:08:24 UTC
adding to

Bug 125077 (row-height-regressions) - [META] regressions introduced by row height recalculation on document load
Comment 2 BogdanB 2019-09-13 11:05:34 UTC
I confirm it happend on Windows on 6.2.
Comment 3 Xisco Faulí 2019-09-17 13:44:41 UTC
we can consider it a dupe of bug 123034 or bug 123971

*** This bug has been marked as a duplicate of bug 123034 ***