W3C home > Mailing lists > Public > www-style@w3.org > November 2011

Re: [css3-multicol] should spanner margins collapse?

From: Florian Rivoal <florianr@opera.com>
Date: Tue, 29 Nov 2011 13:11:15 +0100
To: www-style@w3.org
Message-ID: <op.v5pis1nv4p7avi@localhost.localdomain>
On Mon, 28 Nov 2011 15:19:24 +0100, Anton Prowse <prowse@moonhenge.net>  
wrote:

>> It would also mean
>> that floaters that extend beyond the boundaries of the spanning
>> element will affect the following spanning element's content...
>
> This is true... but that's the case with consecutive headings that  
> contain a float in the normal block formatting model anyhow.

Also, should that not be the desired behavior, it can be turned off using
overflow:hidden. I am not sure it could be manually turned on if we chose
proposition B instead.

>> Advocating for this option means to only consider the case when the
>> column spanning element is an immediate child of multi-column element
>> which is a restriction that is not imposed by the current spec (nor
>> should it be).
>
> Such an unrestricted model doesn't make much sense to me anyway.  Surely  
> only elements which participate in the block formatting context of one  
> of the columns should be allowed to span.  What are the use cases for  
> allowing spanning from within a nested BFC?  What does it mean for an  
> element inside an inline-block or overflow-scroll or floated or abspos  
> column content element to span the columns?

I haven't thought about this as deeply as I probably should, but my first
reaction is that I would have no problem banning spanning on elements that
don't participate in the BFC of one of the columns.

  - Florian
Received on Tuesday, 29 November 2011 12:11:49 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:46 GMT