https://issues.apache.org/bugzilla/show_bug.cgi?id=44328

Andreas L. Delmelle <adelme...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #26801|0                           |1
        is obsolete|                            |

--- Comment #6 from Andreas L. Delmelle <adelme...@apache.org> 2011-03-28 
16:52:00 EDT ---
Created an attachment (id=26807)
 --> (https://issues.apache.org/bugzilla/attachment.cgi?id=26807)
updated test, showing additional issue


The partial fix does not yet correct the behavior in the newly added second
case. If a regular text paragraph is followed by a child block, "widows" would
not apply to the last 2 lines of the first paragraph, as they are not 'in the
last area' generated by the parent block. The algorithm would be allowed to
break before the last line of that paragraph.

A similar issue is demonstrated for orphans in the fourth test.

Conclusion: orphans/widows can only be reliably taken into account by the
LineLayoutManager if there really is no more content preceding/following. If
there is, it seems best to leave it up to the parent BlockLayoutManager to sort
out how many 'lines'[*] need to be kept together.

[*] Note: quoted, since it is ambiguous for nested inline-block content,
especially for lists and tables, where the boxes do not really represent
'lines', but rather list-item- or table-parts. Perhaps list/table content
should be excluded in some way, since it is already handled by
fox:widow-content-limit and fox:orphan-content-limit...?

-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

Reply via email to