Bug 161505 - table/column/text formatting is lost if rows are inserted
Summary: table/column/text formatting is lost if rows are inserted
Status: RESOLVED DUPLICATE of bug 126008
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
24.2.4.2 release
Hardware: x86-64 (AMD64) macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-11 10:16 UTC by Paul Hubert
Modified: 2024-06-11 11:01 UTC (History)
1 user (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 Paul Hubert 2024-06-11 10:16:55 UTC
Description:
Whenever I insert rows in a table, ALL my formatting within the table is LOST.
This may apply to row deletion as well.

Steps to Reproduce:
1.create a table in Write
2.change column / text characteristics (center, bold, color selection, etc.)
3.modify table (e.g. insert a row)
4.formatting is LOST

Actual Results:
1.create a table in Write
2.change column / text characteristics (center, bold, color selection, etc.)
3.modify table (e.g. insert a row)
4.formatting is LOST

Expected Results:
Formatting should PERSIST


Reproducible: Always


User Profile Reset: No

Additional Info:
Every time I make a change to the table, any formatting I've entered for text, columns, or rows is LOST and I must reenter ALL my formatting (centering columns, changing font for a title row, etc.)

This is a fresh install of 24.2.4.2 over the previous release.
Comment 1 johnks 2024-06-11 10:38:51 UTC
unable to reproduce 

Version: 24.2.3.2 (X86_64) / LibreOffice Community
Build ID: 433d9c2ded56988e8a90e6b2e771ee4e6a5ab2ba
CPU threads: 4; OS: Linux 6.5; UI render: default; VCL: gtk3
Locale: en-IN (en_IN); UI: en-US
Calc: threaded
Comment 2 Stéphane Guillou (stragu) 2024-06-11 11:01:30 UTC
Thanks for the report. I assume this happens when using a Table Style.
This is a long-standing issue that is tracked in bug 126008. Marking as duplicate.

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