Peter,
thanks for the answer.
I have always *assumed* that column balancing is implied whenever
top-level block children of a flow have different span attributes,
because it's the only approach that makes sense. If your second
scenario were intended, then the 'span=all' block could not
From: Arnd Beißner [EMAIL PROTECTED]
snip/
Since the default behaviour really seems to be unspecified, and since
there's no property to specify it,
I believe overall less harm is done if you don't balance at the end of the
flow. This is because then you
can always trick the renderer into
Arnd Beißner wrote:
Peter,
thanks for the answer.
I have always *assumed* that column balancing is implied whenever
top-level block children of a flow have different span attributes,
because it's the only approach that makes sense. If your second
scenario were intended, then the 'span=all'
Hi,
I just decided that I can't figure out what - according to the standard -
should exactly happen if you have multiple columns in your body region and
mix top-level fo:blocks of span=all with others of span=1. Perhaps one of
you already found something...
I can see how the
Arnd Beißner wrote:
Hi,
I just decided that I can't figure out what - according to the standard -
should exactly happen if you have multiple columns in your body region and
mix top-level fo:blocks of span=all with others of span=1. Perhaps one of
you already found something...
I can see how
Peter B. West wrote:
Arnd Beißner wrote:
...
Scenarios: (always column-count=3)
Scenario 1 (just blocks with span=all):
ABC
ABC
ABC
ok, no problems.
Scenario 2 (block with span=all, then blocks with span=1)
AAA
BCD
BCD
clear so far.
Scenario 3 (blocks with span=1, THEN 1 block with span=all
