Bug 104027 - FILEOPEN: DOC: enlarged size of several empty paragraphs means the content no longer fits on one page
Summary: FILEOPEN: DOC: enlarged size of several empty paragraphs means the content no...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected)
4.4 all versions
Hardware: All All
: medium normal
Assignee: Not Assigned
Keywords: bibisected, bisected, filter:doc, regression
: 104616 116427 (view as bug list)
Depends on:
Blocks: Writer-Page-Break DOC-Paragraph Regressions-705a8c22
  Show dependency treegraph
Reported: 2016-11-19 11:07 UTC by Xisco Faulí
Modified: 2023-11-01 13:06 UTC (History)
6 users (show)

See Also:
Crash report or crash signature:

sample (165.00 KB, application/msword)
2016-11-19 11:07 UTC, Xisco Faulí
sample2 (194.50 KB, application/msword)
2016-11-19 11:51 UTC, Xisco Faulí
sample3 (64.00 KB, application/msword)
2016-12-01 22:46 UTC, Xisco Faulí

Note You need to log in before you can comment on or make changes to this bug.
Description Xisco Faulí 2016-11-19 11:07:56 UTC
Created attachment 128860 [details]

1. Open the attached file
2. Check second page 

Observed behaviour: content from second page is moved to the next page

Reproduced in 

Build ID: 757a60d01dd152aadab2ba3c8224252481ce8a88
CPU Threads: 4; OS Version: Linux 4.8; UI Render: default; VCL: gtk3; Layout
Engine: new; 
Locale: ca-ES (ca_ES.UTF-8); Calc: group

but not in

Build ID: c15927f20d4727c3b8de68497b6949e72f9e6e9e
Comment 1 Xisco Faulí 2016-11-19 11:10:59 UTC
Regression introduced by:

author	Caolán McNamara <caolanm@redhat.com>	2014-09-23 19:35:50 (GMT)
committer	Caolán McNamara <caolanm@redhat.com>	2014-09-24 09:04:48 (GMT)
commit 705a8c226aee3e68db492083b7cf8b704335328b (patch)
tree c701b3a13f48f6d5a4c226bcf4f67e1e91a41049
parent 6332c643016ce4c4d254c8429a5eceae6664bf5c (diff)

WW8PLCFMan::AdjustEnds deeply flawed concept wrt change tracking
The whole idea of clipping the char attributes to before the cr that word uses
as the end of para marker is flawed from especially the perspective of
redlining which is a char property in word.

If the redline encompasses the newline in order to state that it is deleted,
then if the prop is clipped to before that newline then the end-of-para doesn't
get marked as deleted

For now just remove the character attributes clipping from here to be as
conservative as possible.

Hopefully the ordering of processing start pap before start chp and end chp
before end pap and the other million improvements in the parser that came about
after AdjustEnds was created avoids whatever problems were trying to be worked
around here.

Adding Cc: to Caolán McNamara
Comment 2 Xisco Faulí 2016-11-19 11:51:17 UTC
Created attachment 128866 [details]

Another document affected by the same commit
Comment 3 Xisco Faulí 2016-11-19 13:55:48 UTC
This document attachment 44627 [details] is slightly affected by the same commit too
Comment 4 Xisco Faulí 2016-12-01 22:46:20 UTC
Created attachment 129213 [details]

another document affected by the same commit
Comment 5 Xisco Faulí 2016-12-16 15:46:05 UTC
*** Bug 104616 has been marked as a duplicate of this bug. ***
Comment 6 Xisco Faulí 2017-09-05 22:33:18 UTC
*** Bug 111802 has been marked as a duplicate of this bug. ***
Comment 7 Xisco Faulí 2018-03-20 00:50:59 UTC
*** Bug 116427 has been marked as a duplicate of this bug. ***
Comment 8 QA Administrators 2023-03-18 03:27:50 UTC
Dear Xisco Faulí,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)

If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword

Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team