Sent by Philippe Wittenbergh on 3 February 2006 08:08
On 3 Feb 2006, at 4:42 pm, Christian Montoya wrote:
>> In my test case above, Firefox (1.5) and Safari (1.0 and up) are
>> correct.
>
> Now that I see the latest standard, I concur. At least, as far as I
> can interpret it, that is:
>
> "clear" means add to the top margin a value equal to the height of the
> clear. If the margin is less than the height of the clear, then the
> added value will always result in the height of the clear, and it will
> always look the same. Only when the margin is greater than the height
> of the clear, nothing is added.
>
> So the first case is 0 + 80 = 80.
> The next is 80 + 0 = 80.
> The next is 100 + 0 = 100.
> The last is -1 + 81 = 80.
That is the correct assessment for the value of the computed margin-
top in those cases.
>
> Not a very helpful implementation I guess?
?
The css 2.1 wording is quite clear, I think. As far as
implementations go, Opera has still some work to do, and IE maybe
(depending on how IE 7 handles margins, margin-collapsing, etc), and
iCab.
> - Isn't an alternative also
> to give the floated element a bottom margin?
If you want to make sure there is some separation space between the
floated box and the (cleared) subsequent block, that is the way to
go, as you never know how tall (computed height) the floated block
will be, except if the height is locked in pixels (i.e. an image).
Philippe
---
Philippe Wittenbergh
<http://emps.l-c-n.com/>
______________________________________________________________________
css-discuss [EMAIL-REMOVED]]
http://www.css-discuss.org/mailman/listinfo/css-d
IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7
List wiki/FAQ -- http://css-discuss.incutio.com/
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/