W3C home > Mailing lists > Public > www-style@w3.org > October 2010

Re: [css3-multicol] overflow and paging?

From: Håkon Wium Lie <howcome@opera.com>
Date: Wed, 20 Oct 2010 00:12:11 +0200
Message-ID: <19646.6075.963077.695398@gargle.gargle.HOWL>
To: shelby@coolpage.com
Cc: www-style@w3.org
Also sprach Shelby Moore:

 > Thus I offer an optional suggestion to place that in its own section as
 > follows, and I would further be more correct (and clear that column rows
 > are atomic and that page direction overflow is in the block direction) by
 > including the word 'row' (perhaps 'row' bold or italic to emphasize it),
 > this implies that the page is a constraint on the column height too, but
 > you might want to state it explicitly:
 > 8.3 Overflow of page in paged media
 > The page boundary constrains the column height and column rows that do not
 > fit within the page are moved to the next page.

I can't parse that. I can see ways of making it parsable, but I'd
rather have it from you.

 > Or if you prefer to be less verbose and make column height constraint
 > implied (but I prefer the one above):
 > 8.3 Overflow of page in paged media
 > Column rows that do not fit within the page are moved to the next page.

I'm not sure we should include 'row'. The only reason why the row
comes into existance is because the column boxes don't fit, right? So,
rows are created after pagination, not before.

 > 8.2 Overflow outside multicol elements
 > Columns honor 'overflow' and always overflow in the inline direction when
 > the column height is constrained. The column height may be constrained for
 > example by using 'height' or explicit column breaks.

This is not quite correct. It's not the columns that honor 'overflow',
it's the multi-column element.

I'm also trying to minimize the number of changes in the draft. The
draft is a Candidate Recommendation, so only necessary clarifications
should go in.


              Håkon Wium Lie                          CTO °þe®ª
howcome@opera.com                  http://people.opera.com/howcome
Received on Tuesday, 19 October 2010 22:12:52 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:38:39 UTC