Andreas L. Delmelle commented on FOP-2060:

Hmm, I think the expectation of 3 is correct. The empty middle block still 
generates one normal block area, which happens to have no descendant line 
areas. That block area shifts to the next page due to the specified 
The next block's first area then, cannot be the first area on that same page. 
So, in order to satisfy that second break-before, there *has* to be an empty 
second page.
It is definitely not the same situation that is mentioned in the bug at w3.org, 
since that seems to concern cases of nesting.

Now, if the empty block had both break-before and break-after specified, then 
the next block's break-before would be suppressed. In that case, there should 
not be 2 empty pages.

I would say that, yes, the fix stands as in 'fixes the original issue'. It just 
had an unintended side effect that was not covered by the layout engine tests, 
so nothing that could have alerted anyone. No harm done.

> adjoining blocks with break-before="page" break-after="page" cause extra 
> empty page
> -----------------------------------------------------------------------------------
>                 Key: FOP-2060
>                 URL: https://issues.apache.org/jira/browse/FOP-2060
>             Project: FOP
>          Issue Type: Bug
>          Components: layout/unqualified
>    Affects Versions: trunk
>         Environment: Operating System: All
> Platform: All
>            Reporter: Luis Bernardo
>             Fix For: trunk
>         Attachments: 2060-empty-block-issue.xml, test.fo, test.pdf
> This causes five pages instead of four:
>       <fo:block>
>         <fo:block>page 1</fo:block>
>         <fo:block break-before="page" break-after="page">page 2</fo:block>
>         <fo:block break-before="page" break-after="page">page 3</fo:block>
>         <fo:block>page 4</fo:block>
>       </fo:block>
> The empty extra page happens between page 2 and page 3.

This message was sent by Atlassian JIRA

Reply via email to