Bug 149105 - Loss of formatting in tables
Summary: Loss of formatting in tables
Status: RESOLVED DUPLICATE of bug 126008
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.3.3.2 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-05-16 08:41 UTC by harkontes
Modified: 2022-10-17 22:36 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description harkontes 2022-05-16 08:41:52 UTC 
Description:
Adding rows to a table in Writer loses formatting (centered text, bold, alignment, etc.) and must be inserted again.

Steps to Reproduce:
1. insert a table into a Writer document
2. change the table formatting (bold, text alignment, etc.)
3. add new cells / rows / columns to the table

Actual Results:
the entire table has reverted to standard formatting

Expected Results:
add cells / rows / columns keeping the formatting changed


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 7.3.3.2 (x64) / LibreOffice Community
Build ID: d1d0ea68f081ee2800a922cac8f79445e4603348
CPU threads: 2; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win
Locale: it-IT (it_IT); UI: it-IT
Calc: threaded
Comment 1 Greasya 2022-05-21 11:00:45 UTC 
Thank you for reporting the bug. I can not reproduce the bug in Linux 5.4;



Version: 7.4.0.0.alpha0+ / LibreOffice Community
Build ID: 465c3ad95059f0efa13c8027f7383c4d20a5b2ff
CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3
Locale: en-IN (en_IN); UI: en-US
Calc: CL
Comment 2 Dieter 2022-05-21 11:30:12 UTC 
Harkontes, could you please check, if it is a duplicate of bug 126008?
Comment 3 Dieter 2022-05-21 11:30:26 UTC Comment hidden (obsolete)
Comment 4 Rafael Lima 2022-10-17 22:36:00 UTC 

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