Bug ID: 54167
Summary: Overflow recovery doesn't play well with changing IPD
Created attachment 29607
FO file illustrating the issue
The page overflow recovery mechanism consists in pushing the overflowing
content to the next page in the hope that it will be bigger and able to
accommodate the content.
When the IPD of the next page changes, the page breaking algorithm returns
early and AbstractBreaker (doLayout method) splits the content and re-lays out
what follows the page break, according to the new IPD.
Those two mechanisms are in conflict when the overflow occurs at the first
legal break, leading to no too short node and no feasible break.
AbstractBreaker is then asked to split before the content, which it is not
When the flow IPD changes the overflow mechanism must be disabled, since anyway
the line breaking has to be re-done according to the new IPD.
You are receiving this mail because:
You are the assignee for the bug.