Bug 115613 - Reformat table items after adding a new line with default table properties
Summary: Reformat table items after adding a new line with default table properties
Status: RESOLVED DUPLICATE of bug 115573
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.0.0.3 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-10 13:12 UTC by Franz FRANKE
Modified: 2018-02-10 14:25 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
example (180.90 KB, application/x-7z-compressed)
2018-02-10 13:25 UTC, Franz FRANKE 		Details
View All 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 Franz FRANKE 2018-02-10 13:12:51 UTC 
Description:
If you have change the proberties of some table Items. (ex. font, fontsize etc.) and you will now a new table Line after the actual line, all table items will be reformat to Default table properties "Tabelleninhalt"

Sorry for my bad English

Steps to Reproduce:
1.change font or fontsize of some table items
2.add a new table line after the active line
3.check old lines in the table

Actual Results:  
all lines will be reformat to default

Expected Results:
old line properties will not be chaned


Reproducible: Always


User Profile Reset: No



Additional Info:
I have tested this behaviour thin many windows Clients 
Window 10   1705



User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.119 Safari/537.36 OPR/51.0.2830.26
Comment 1 Franz FRANKE 2018-02-10 13:25:01 UTC 
Created attachment 139757 [details]
example
Comment 2 Jacques Guilleron 2018-02-10 14:25:36 UTC 
Hi Franz,

Thank you to have reported it. this bug was however previously reproted in
Bug 115573 - EDITING: Table loses formatting when inserting a new row in a table
I set status to Duplicate.

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