Bug 116963 - writer: format of text is killed when altering cells of a table
Summary: writer: format of text is killed when altering cells of a table
Status: RESOLVED DUPLICATE of bug 115929
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.0.2.1 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-04-12 09:14 UTC by Karsten
Modified: 2018-04-12 09:38 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
Document example (12.29 KB, application/vnd.oasis.opendocument.text)
2018-04-12 09:15 UTC, Karsten 		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 Karsten 2018-04-12 09:14:43 UTC 
Description:
The text format in a table is killed when you alter cells in a table.
This means you add an column or row.

Version: 6.0.2.1
Build-ID: f7f06a8f319e4b62f9bc5095aa112a65d2f3ac89
CPU-Threads: 4; BS: Linux 3.16; UI-Render: Standard; VCL: kde4; 
Gebietsschema: de-DE (de_DE.UTF-8); Calc: CL

Steps to Reproduce:
Go in the last cell and press enter.
Then you will see that the complete format of the text is killed.
Or if you insert a row then it is killed in the same way.
Even after an undo the format keeps destroyed!
So you can't do anything with the table without killing the text formats.


Actual Results:  
Format of the text is overwritten.

Expected Results:
The formatting of the text is not touched when you add columns or rows.


Reproducible: Always


User Profile Reset: No



Additional Info:


User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0
Comment 1 Karsten 2018-04-12 09:15:51 UTC 
Created attachment 141303 [details]
Document example

In this document the problems will occur.
Comment 2 Dieter 2018-04-12 09:38:38 UTC 
This bug is fixed in LO 6.0.3.

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