Issue 88659 - Block mode : wrong position of paragraph created when copy and past
Summary: Block mode : wrong position of paragraph created when copy and past
Alias: None
Product: Writer
Classification: Application
Component: editing (show other issues)
Version: DEV300m9
Hardware: All Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2008-04-23 18:40 UTC by
Modified: 2013-08-07 14:44 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description 2008-04-23 18:40:23 UTC
Steps to reproduce :
In a new document, enter the words pressing Enter after each but the last one:

Clik on Display non printing characters icon.
Change selection to Block mode
Select [Today Yesterday Tomorrow] words without paragraph marks.
Press Ctrl+X (the 3 words are cut, only paragraph marks are left and the word
Press Enter after the word [Selection] to create a new paragraph.
Press Ctrl+C --> you get the word [SelectionToday] the paragraph mark as
disappeared between the two.
The cursor is blinking at the end of the word [Tomorrow] (end of pasted block).
Press Enter, the word [Today] move under the word [Selection] and [Selection] is
followed by a paragraph mark.
The cursor is still blinking at the end of the word [Tomorrow]
Press Enter, a new empty paragraph is created between [Selection] and [Today]

As long as you're in Block mode, all the paragraphs are created at the beginning
of the pasted block.

I'm using Ubuntu 7.10, DEV300m10 with FR langpack, .deb packages from Sun.

Kind regards
Comment 1 eric.savary 2008-04-23 23:39:38 UTC
Thanx Sophie for those findings! :)

Playing around with your example I've found about 3 other related bugs :(

I'll have to have a deeper look at it...

In the midtime, workaround: switch to "Standard" selection before pasting. 
Comment 2 eric.savary 2008-09-12 23:29:05 UTC
@AMA: everything I found seem to be related to the same bug.
Please have a look.