W3C home > Mailing lists > Public > www-style@w3.org > January 2012

RE: [CSS21] BFC may become narrower and collide with a previous float

From: Rossen Atanassov <Rossen.Atanassov@microsoft.com>
Date: Mon, 30 Jan 2012 19:10:51 +0000
To: Alan Gresley <alan@css-class.com>, Morten Stenshorne <mstensho@opera.com>
CC: fantasai <fantasai.lists@inkedblade.net>, "www-style@w3.org" <www-style@w3.org>
Message-ID: <9A57384B9CE9AE4F9C01F3BB5C3D88440DFDC1@TK5EX14MBXW603.wingroup.windeploy.ntdev.microsoft.com>
> -----Original Message-----
> From: Alan Gresley [mailto:alan@css-class.com]
> Sent: Friday, January 27, 2012 3:46 AM
> This rule does not apply. If a BFC can fit beside the first float, then it will flow
> beside it. Read this part of the spec.
>    | If necessary, implementations should clear the
>    | said element by placing it below any preceding
>    | floats, but may place it adjacent to such floats
>    | if there is *sufficient space*.
> There is *sufficient space* for the BFC in your two test case as well as the
> examples in this test case.

As Fantasai already pointed out, the keyword here is sufficient *space* not *width*. In her test case the table BFC has specified, computed and used height of 300px which will results in a collision with the right (blue) floater box regardless of its width, thus the rule applies and the BFC should be cleared. If you don't think this is true, can you be more specific (in the context of the original example) as to why the space should be sufficient?

Fantasai's example http://lists.w3.org/Archives/Public/www-archive/2012Jan/att-0035/foo.html 

Received on Monday, 30 January 2012 19:11:42 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:10 UTC