Bug 115929 - TABLE: Formatting lost when adding or deleting a row
Summary: TABLE: Formatting lost when adding or deleting a row
Status: RESOLVED DUPLICATE of bug 115573
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.0.1.1 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
: 116963 (view as bug list)
Depends on:
Blocks: Cell-Add-Delete
  Show dependency tree / graph
 
Reported: 2018-02-22 05:11 UTC by simonefranceschini
Modified: 2018-04-12 10:49 UTC (History)
1 user (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 simonefranceschini 2018-02-22 05:11:01 UTC 
Description:
When I add/delete a row/column in a table, formattation of characters (e.g. bold, dimensions) is lost and get back to the default values 

Steps to Reproduce:
1. Create a table
2. Change dimension of characters
3. Add/delete a row

Actual Results:  
Formattation set back to default values

Expected Results:
Keeping the given formattation


Reproducible: Always


User Profile Reset: No



Additional Info:


User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:58.0) Gecko/20100101 Firefox/58.0
Comment 1 Dieter 2018-02-22 07:35:34 UTC 
I confirm this with

Version: 6.1.0.0.alpha0+ (x64)
Build ID: 77a535285f0fd5f2464430abdc67cf99be024868
CPU threads: 4; OS: Windows 10.0; UI render: GL; 
TinderBox: Win-x86_64@42, Branch:master, Time: 2018-01-23_23:04:23
Locale: de-DE (de_DE); Calc: CL

additional informations:
- UNDO is not possible
- it is independend from the way you add a row
Comment 2 Telesto 2018-02-22 07:52:57 UTC 

*** This bug has been marked as a duplicate of bug 115573 ***
Comment 3 Dieter 2018-04-12 09:38:38 UTC 
*** Bug 116963 has been marked as a duplicate of this bug. ***
Comment 4 Karsten 2018-04-12 10:49:08 UTC 
O.K. Please tell me in which version this should have been fixed?