W3C home > Mailing lists > Public > www-style@w3.org > May 2007

RE: [css3-gcpm] Multi-column floats overflowing the column

From: Alex Mogilevsky <alexmog@exchange.microsoft.com>
Date: Fri, 4 May 2007 11:42:52 -0700
To: Brady Duga <duga@ljug.com>
CC: W3C CSS <www-style@w3.org>
Message-ID: <04F36FB4ED0F85459AA447F72711526FD62FE94BC7@DF-GRTDANE-MSG.exchange.corp.microsoft.com>

I agree, it is a good idea to state explicitly that floats override the clipping behavior of columns.

-----Original Message-----
From: Brady Duga [mailto:duga@ljug.com]
Sent: Friday, May 04, 2007 11:32 AM
To: Alex Mogilevsky
Cc: Brady Duga; W3C CSS
Subject: Re: [css3-gcpm] Multi-column floats overflowing the column


On May 4, 2007, at 11:21 AM, Alex Mogilevsky wrote:

>
> There is no contradiction here. GCPM defines new kinds of float
> behavior, specifically with the intent of overriding clipping
> behavior of columns. Therefore definition of how these new floats
> interact with other objects (including columns) belongs in GCPM.

That's fine - I'm not saying it shouldn't be allowed to flow out of
the columns, but I do see a contradiction (or at least potential
confusion) in the current wording. The draft says it extends the
functionality of the multi-column spec, not that it replaces it.
Since the multi-column spec says things get clipped and this draft
never explicitly modifies that constraint, it appears that it should
still be in place. I would like to see some text explaining when (for
paged media) it is allowed for floated content to flow into
neighboring columns. Always? Only when using one of the new float
values? Only when float-offset is specified?

--Brady
Received on Friday, 4 May 2007 18:43:11 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:54:50 GMT