Bug 37813 - span property causes random insertion of page breaks
Summary: span property causes random insertion of page breaks
Status: CLOSED FIXED
Alias: None
Product: Fop - Now in Jira
Classification: Unclassified
Component: page-master/layout (show other bugs)
Version: 0.90
Hardware: Other Windows XP
: P2 normal
Target Milestone: ---
Assignee: fop-dev
URL: http://xml.apache.org/fop
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-06 23:00 UTC by Matt LeClair
Modified: 2012-04-01 07:07 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Matt LeClair 2005-12-06 23:00:11 UTC
If I create three blocks on a page and make the first and third set to
span="all", a page break will be added.  This pattern will continue for as many
alternating blocks as I include.

I need to create a heading that SPANS two columns, followed by some text IN
columns, repeated.  It works fine for the first two fo:blocks, but after that it
begins added page breaks in weird places.  Also, this behavior will occur even
with column-count="1" instead of "2".  The problem starts with the second
<fo:block span="all"> element.

I tried to fix this by using multiple region-body elements, but it failed.  Code
below...


<?xml version="1.0" encoding="UTF-8"?>
<fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format"
xmlns:r="http://xmlresume.sourceforge.net/resume/0.0">
	<fo:layout-master-set>
		<fo:simple-page-master page-width="8.5in" page-height="11in"
master-name="resume-page">
			<fo:region-body column-count="2"/>
		</fo:simple-page-master>
	</fo:layout-master-set>
	<fo:page-sequence master-reference="resume-page">
		<fo:flow flow-name="xsl-region-body" line-height="normal">
			<fo:block span="all">Test Spanned Block</fo:block>
			<fo:block span="none">Test Unspanned Block Test Unspanned Block Test
Unspanned Block Test Unspanned Block</fo:block>
			<!-- this one causes the error -->
			<fo:block span="all">Test Spanned Block</fo:block>
			<!-- this one doesn't -->
			<!-- <fo:block span="none">Test Spanned Block</fo:block> -->
		</fo:flow>
	</fo:page-sequence>
</fo:root>
<!--  Failed Solution
<?xml version="1.0" encoding="UTF-8"?>
<fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format"
xmlns:r="http://xmlresume.sourceforge.net/resume/0.0">
	<fo:layout-master-set>
		<fo:simple-page-master page-width="8.5in" page-height="11in"
master-name="resume-page-A">
			<fo:region-body/>
		</fo:simple-page-master>
		<fo:simple-page-master page-width="8.5in" page-height="11in"
master-name="resume-page-B">
			<fo:region-body column-count="2"/>
		</fo:simple-page-master>
	</fo:layout-master-set>
	<fo:page-sequence master-reference="resume-page-A">
		<fo:flow flow-name="xsl-region-body" line-height="normal">
			<fo:block>Test Spanned Block</fo:block>
		</fo:flow>		
	</fo:page-sequence>
	<fo:page-sequence master-reference="resume-page-B">
		<fo:flow flow-name="xsl-region-body" line-height="normal">
			<fo:block>Test Unspanned Block Test Unspanned Block Test Unspanned Block Test
Unspanned Block</fo:block>
		</fo:flow>		
	</fo:page-sequence>
	<fo:page-sequence master-reference="resume-page-A">
		<fo:flow flow-name="xsl-region-body" line-height="normal">
			<fo:block>Test Spanned Block</fo:block>
		</fo:flow>		
	</fo:page-sequence>	
</fo:root> -->
Comment 1 Jeremias Maerki 2005-12-07 10:04:57 UTC
Bug fixed in Subversion: http://svn.apache.org/viewcvs?rev=354752&view=rev

Thanks for reporting it.
Comment 2 Tim Junker 2006-04-01 21:56:36 UTC
At version .91 Beta
Within a multi column page master 
Within a <fo:block span="all"> a <table> that spans pages reverts to multi 
column on second and subsequent pages.
Comment 3 Jeremias Maerki 2006-04-10 09:45:47 UTC
(In reply to comment #2)
> At version .91 Beta
> Within a multi column page master 
> Within a <fo:block span="all"> a <table> that spans pages reverts to multi 
> column on second and subsequent pages.

Please don't reuse existing Bugzilla entries if it's not a regression. You're
not reporting the same bug. Please open a new entry and don't forget to attach a
full FO file (not XSLT) that shows the problem.
Comment 4 Glenn Adams 2012-04-01 07:07:27 UTC
batch transition pre-FOP1.0 resolved+fixed bugs to closed+fixed