Bug 46322 - spanning block in second column is not moved to next page
Summary: spanning block in second column is not moved to next page
Status: NEW
Alias: None
Product: Fop - Now in Jira
Classification: Unclassified
Component: pdf (show other bugs)
Version: trunk
Hardware: PC Windows Server 2003
: P3 normal
Target Milestone: ---
Assignee: fop-dev
URL:
Keywords:
Depends on:
Blocks: 46315
  Show dependency tree
 
Reported: 2008-12-02 06:23 UTC by Georg Datterl
Modified: 2012-04-13 09:53 UTC (History)
0 users


Attachments
Testcase (2.86 KB, text/plain)
2008-12-02 06:24 UTC, Georg Datterl 		Details
Testcase file fit for /test/layoutengine/standard-testcases (7.96 KB, text/plain)
2009-01-09 06:18 UTC, Georg Datterl 		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 Georg Datterl 2008-12-02 06:23:16 UTC 
In a two-column layout, a spanning block in the second column of page 1 is expected to be moved to the start of page 2. 

Bug: the first line of the spanning block is displayed on page 1, ignoring the orphans setting (default and explicit) and the bottom margin. 

Given a big enough font size (see example) it is even possible to see only the upper half of the line. The layout errors on the second page are related to this, I assume.
Comment 1 Georg Datterl 2008-12-02 06:24:26 UTC 
Created attachment 22977 [details]
Testcase
Comment 2 Vincent Hennebert 2008-12-03 02:52:45 UTC 
Hi Georg,

Thanks for the bug report and the very illustrative example.

Although that's all I can say for now :-\ Maybe this is best to delay the solving of this issue until the new layout method is implemented.

Vincent
Comment 3 Georg Datterl 2009-01-09 06:18:10 UTC 
Created attachment 23099 [details]
Testcase file fit for /test/layoutengine/standard-testcases

Since I had it at hand, it may save time later
Comment 4 Andreas L. Delmelle 2011-03-27 02:55:08 UTC 
Not entirely sure, yet whether it is related, but I just posted a patch in Bugzilla 44328 which might address the issue. (Another distinct possibility is that it was already fixed by the patch for Bugzilla 49835, but just not closed yet. Will check that later.)

At any rate, the sample produces the expected output in my current sandbox.
Comment 5 Glenn Adams 2012-04-07 01:44:49 UTC 
resetting P2 open bugs to P3 pending further review
Comment 6 Glenn Adams 2012-04-11 06:18:11 UTC 
change status from ASSIGNED to NEW for consistency
Comment 7 Pascal Sancho 2012-04-13 09:51:02 UTC 
provided test case, Glenn.
Comment 8 Pascal Sancho 2012-04-13 09:53:08 UTC 
(In reply to comment #7)
> provided test case, Glenn.

sorry, comment related to wrong issue