Bug 162668 - FORMATTING Calc ignores Wrap Text Automatically when set for entire column after save and close
Summary: FORMATTING Calc ignores Wrap Text Automatically when set for entire column af...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
24.2.2.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, bisected, regression
Depends on:
Blocks:
 
Reported: 2024-08-28 15:23 UTC by dhuck
Modified: 2024-09-05 22:42 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 dhuck 2024-08-28 15:23:15 UTC
Description:
After I re-open a Calc document, old, blank entries with the "Wrap Text Automatically" checkbox selected stay wrapped, but new entries do not wrap. 

This only occurs when I apply the property after I click the column header and right-click to apply the property to the entire column, then save and re-open. When I select a subset of the column (like F0 to F200) that includes blank entries, the "Wrap Text Automatically" will stay applied down to that row even after multiple saves and reopens.

Steps to Reproduce:
1. Select column header.
2. Right-click, go to properties, and check "Wrap Text Automatically"
3. Save and re-open.

Actual Results:
The blank cells in the column revert to not wrapping text automatically.

Expected Results:
The blank cells in the column should retain the "Wrap Text Automatically" setting.


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Using a portable installation. Saving/editing XLXS
Comment 1 ady 2024-08-28 15:53:23 UTC
Known issue. There are so many reports (both old and recent, regressions and inherited) about Wrap Text (with ODS, XLSX, and/or XLS) that I don't even know which of those should be pointed to as original of this dupe.
Comment 2 dhuck 2024-08-28 16:27:45 UTC Comment hidden (obsolete)
Comment 3 ady 2024-08-28 17:10:12 UTC
Bug 97106 (inherited) is not the same as this bug 162668, although both are related to Wrap Text.

Following the STR from comment 0, this is a regression introduced in LO 24.2. In LO 7.6 the Wrap Text property is saved to XLSX and read correctly when re-opened.

As mentioned, there are several possible original reports that could be pointed-to from this dupe, but bug 97106 is not one of those.
Comment 4 raal 2024-09-04 15:38:26 UTC Comment hidden (obsolete)
Comment 5 Caolán McNamara 2024-09-04 19:48:45 UTC Comment hidden (obsolete)
Comment 6 raal 2024-09-05 21:21:39 UTC
This seems to have begun at the below commit in bibisect repository/OS linux-64-24.2.
Adding Cc: to Paris Oplopoios ; Could you possibly take a look at this one?
Thanks
 0fd3d8fa5041781bea37aeda264bda71a66c6152 is the first bad commit
commit 0fd3d8fa5041781bea37aeda264bda71a66c6152
Author: Jenkins Build User <tdf@pollux.tdf>
Date:   Mon Aug 28 10:38:53 2023 +0200

    source 1760ee4d328cfb6ba22a5b3c84016625b12adb25

155970: sc: Fix wrapText not being applied correctly on export | https://gerrit.libreoffice.org/c/core/+/155970
Comment 7 ady 2024-09-05 22:18:16 UTC
Please allow me to point out, once again – I'm not counting them anymore – that Paris is not likely to reply to any of the several regressions in a timely manner.

Someone else (perhaps also from collabora) should rather take a look at these regressions.

Part of the regressions were already patched in some way or another in some of the other regression-reports, but clearly not all the regressions are corrected ATM – searching according to "Regression By" limited to Calc module might help.

Some of the original causes (but reverting them might no longer be possible, giving the additional commits to patch these):


 <https://gerrit.libreoffice.org/c/core/+/155970> 

 <https://gerrit.libreoffice.org/c/core/+/158702> 

 <https://gerrit.libreoffice.org/c/core/+/159758>
Comment 8 ady 2024-09-05 22:42:13 UTC
Some regression reports were already fixed. ATM, we still have (at least) bugs 160900, 161453, bug 159690 comment 17, and this tdf#162668 (plus respective dupes).