Apache OpenOffice (AOO) Bugzilla – Issue 93638
Copying of paragraph with page-break property changed behaviour from 2.4.1 to 3.0
Last modified: 2017-05-20 10:15:11 UTC
- load attached document - copy the note, e.g. by doing Ctrl-A, Ctrl-C - leave selection, hit enter for a new line - paste -> not only the selection including the note is inserted into the document, but a page break as well mod->cmc: any idea? this does not seems to happen with new notes, only with the imported note, .doc- file was created in Word 2000
Created attachment 56337 [details] bug doc created in Word 2000
I'll build up m31 to check this, but it might not be related to the comment, but related to the (hopefully unchanged in the filter, and perhaps changed in cut-and-paste) page-break-before property of the first paragraph.
Yeah, its a generic thing. See the next attached .odt. In 2.4.1 copying a paragraph with page-break before in this situation would create a new paragraph *without* the page-break before property. While in 3.0 and in DEV300_m31 the page-break before gets copied as well. I don't know if the *old* behaviour was a bug in that the property got lost, or if the old behaviour was a special desired case which has become lost.
Created attachment 56367 [details] sample native document, with no notes
Not specific to notes, I'll return this to the pool of untriaged-bugs for qa to decide if the old or new behaviour is the wrong one :-)
That property gets copied too if you copy only a portion of the paragraph--say one word of it, or one character. I think only character properties should be copied in that case--or am I wrong?
MRU->ES: that's true, see CMC's attachment. The page break was not copy/pasted in OO 2.4.1. Did this change intentionally?
@AMA: issue 90123 is the opposite of this one. Please have a look at both.
*** Issue 96223 has been marked as a duplicate of this issue. ***
Due to our workload and resources (development as well as QA) I've to retarget this issue to OOo3.2.
Oliver, please take over
Target changed to 3.x
I could not find out when or where the handling has been changed. But it absolutely makes sense to handle the break attributes the same way as any paragraph attribute. You can always find usage scenarios that prefer either the new or the old behavior.