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

Re: Float Model

From: Ph. Wittenbergh <jk7r-obt@asahi-net.or.jp>
Date: Mon, 6 Oct 2008 10:56:49 +0900
Cc: Keiji Ikari <kei@teamikaria.com>
Message-Id: <623E631A-C11E-432D-8E8F-5747BE4D4319@asahi-net.or.jp>
To: W3C Style List <www-style@w3.org>


On Oct 4, 2008, at 7:19 AM, Keiji Ikari wrote:

>
>> From http://www.w3.org/TR/2008/REC-CSS2-20080411/ 
>> visuren.html#floats :
>
> "Since a float is not in the flow, non-positioned block boxes created
> before and after the float box flow vertically as if the float didn't
> exist. However, line boxes created next to the float are shortened to
> make room for the floated box. Any content in the current line before
> a floated box is reflowed in the first available line on the other
> side of the float."
>
> "When a block box overlaps, the background and borders of the block
> box are rendered behind the float and are only be visible where the
> box is transparent. The content of the block box is rendered in front
> of the float."
>
> As you may or may not know IE ignores this definition (see
> http://www.positioniseverything.net/explorer/floatmodel.html ) and
> wraps both inline and block elements.

That is not true. Or at least not completely true: IE 6 & 7 ignore  
that definition (only) when 'haslayout' is triggered on the static,  
non-floated block (e.g. using width). And in that case the non-floated  
block is displaced, not wrapped around the float.
That IE behaviour is somewhat similar to what CSS 2.1 compliant  
browsers do when the non-floated block establishes a new block- 
formatting context (per 9.4.1).


Philippe
---
Philippe Wittenbergh
http://l-c-n.com/
Received on Monday, 6 October 2008 01:57:26 GMT

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