--- Comment #4 from Andreas L. Delmelle <>  2009-05-06 
10:16:07 PST ---
(In reply to comment #3)
> The bug is this second penalty that shouldn't be generated in the first place,
> since breaks win over keeps. There may be an opportunity to fix that in the
> same time as bug #46905.

Agreed. As I remember from another similar issue I fixed recently in
FlowLayoutManager, it could turn out to be a very straightforward fix. I'll see
if I can confirm later tonight.
At some point in getNextKnuthElements(), the parentLM adds a break in between
the sequences returned by two consecutive childLMs. It's likely to be a simple
matter of :

if (!ElementListUtils.endsWithForcedBreak(returnedList)) {
  //add in-between break

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

Reply via email to