Download it now!
Bug 105550 - FORMATTING Pasting text changes paragraph format in older LO document
Summary: FORMATTING Pasting text changes paragraph format in older LO document
Status: RESOLVED DUPLICATE of bug 77651
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.1.4.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: needsUXEval
Depends on:
Blocks:
 
Reported: 2017-01-26 16:14 UTC by Ulrich Gemkow
Modified: 2020-03-16 13:18 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Test document (11.79 KB, application/vnd.oasis.opendocument.text)
2017-01-26 16:14 UTC, Ulrich Gemkow
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ulrich Gemkow 2017-01-26 16:14:26 UTC
Created attachment 130705 [details]
Test document

Pasting text (ctrl-v) in an paragraph which has a modified style changes the paragraph style.

To reproduce

- Open the attached example document

- Select a few chars in the indented text

- Copy the chars (ctrl-c)

- Paste (ctrl-v) in the middle of the indented paragraph

The style of the paragraph changes which should not happen. It is not obvious which attributes are changed.

The "list bullet style" is custom-made. I was not able to reproduce this with a "bare example". I have no idea what happens.

The bug only happens when pasting, not when typing.
Comment 1 Vitaliy 2017-01-27 10:56:06 UTC
Reproduced it. Taking
Comment 2 Vitaliy 2017-01-27 10:56:29 UTC Comment hidden (me-too, obsolete)
Comment 3 Ulrich Gemkow 2017-08-10 20:06:47 UTC
Further investigation shows that this is a problem with an old LO document opened in a new LO release:

The attached document was created with a older LO release which had not yet separated the list styles from the "Styles and Formatting" list of styles. For this document the list format was modified in the paragraph styles with the old LO release.

When editing the old document in the current LO release the changing of the paragraph "auto-assigns" the list style to the paragraph and this style is different from the old modified list style.

When opening the attached document in the current LO release you see that the list styles are in both lists.

I cannot judge what would be the correct behaviour. IMHO it would be correct to copy the "old" list styles to the new ones when opening an old document to be backward compatible. Or is the current behaviour intended?

[Unfortunately I cannot determine which old LO release was the creator of the document, the document was changed several times with different LO releases]
Comment 4 QA Administrators 2018-08-18 02:38:49 UTC Comment hidden (obsolete)
Comment 5 Ulrich Gemkow 2020-03-08 20:54:38 UTC
This bug is still present

Version: 6.4.1.2
Build ID: 1:6.4.1~rc2-0ubuntu0.18.04.1
CPU threads: 4; OS: Linux 5.3; UI render: default; VCL: kf5; 
Locale: de-DE (en_US.UTF-8); UI-Language: en-US
Calc: threaded
Comment 6 Heiko Tietze 2020-03-12 07:47:45 UTC
When you paste into an empty paragraph the source paragraph style will be used. If the target is not empty, for example when you add a single space, the target style will be used. That applies only to paragraph styles, of course. The discussion runs on bug 98381 and bug 100018.

*** This bug has been marked as a duplicate of bug 98381 ***
Comment 7 Ulrich Gemkow 2020-03-15 07:35:04 UTC
Thanks for looking into this. But this is IMHO not the same as #98381 and not handled there.

Take the test document, select a few character _inside_ of the paragraph, press Ctrl-C and then inside the same paragraph press Ctrl-V and the style changes.

This is text from the same paragraph pasted inside the same paragraph.

This behavior can IMHO never be correct, it is not what a user expects.

Thanks again!
Comment 8 Heiko Tietze 2020-03-16 13:18:58 UTC
True, this one was wrong. But a bug like this has been reported before with high probability and I found some relevant issues. No idea what exactly goes wrong here.

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