Bug 46240 - break-before breaks span
Summary: break-before breaks span
Status: CLOSED FIXED
Alias: None
Product: Fop - Now in Jira
Classification: Unclassified
Component: page-master/layout (show other bugs)
Version: trunk
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: fop-dev
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-19 01:21 UTC by Georg Datterl
Modified: 2012-04-01 06:39 UTC (History)
0 users



Attachments
Test case (1.33 KB, text/plain)
2008-11-19 01:22 UTC, Georg Datterl
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Georg Datterl 2008-11-19 01:21:28 UTC
Attached you will find a small fo-file containing one simple page master and two pages. Although the page master has a column-count=2, both pages should be single-column, therefore span=all is used. Both pages should start at an odd page, therefore  break-before=odd-page is used. 

The unexpected result: The text on the first page uses both columns, the second page is empty, but the text on the third page uses only one column. When I remove the first page or break-before, the second text uses both columns.
Comment 1 Georg Datterl 2008-11-19 01:22:35 UTC
Created attachment 22891 [details]
Test case
Comment 2 Andreas L. Delmelle 2008-11-19 12:02:18 UTC
Doing a bit of preliminary debugging, the problem seems to be that (see FlowLM.getNextKnuthElements()):

a) the span change is detected (FlowLM.currentSpan == EN_ALL), so the returnList is handed over to the PageBreaker
b) the next time it is called, currentSpan will already be EN_ALL, so no span change, but ... AbstractBreaker.getNextBlockList() will have explicitly reset the LayoutContext a bit earlier on (signalSpanChange(NOT_SET)), so the processing continues as if no span had been specified
Comment 3 Andreas L. Delmelle 2008-11-19 14:46:30 UTC
Fixed in FOP trunk, see r719110.

Thanks for reporting!
Comment 4 Glenn Adams 2012-04-01 06:39:36 UTC
batch transition pre-FOP1.0 resolved+fixed bugs to closed+fixed