> I see indeed that Firefox ignores a negative margin on the same side > of the float as well. > > > The spec deliberately not very precise about these cases. At > http://www.w3.org/TR/CSS21/visuren.html#bfc-next-to-float > there is > "CSS2 does not define when a UA may put said element next to the float > or by how much said element may become narrower" > > So the UA are "allowed" to make those bfc "narrower" as they like :-) > > > Moreover, the spec now says: > "the _border box_ of a table, block-level replaced element, or element > in the normal flow that establishes a new block formatting context > must not overlap any floats in the same block formatting context". > > They mention the "border box" and not the "margin box", so at least on > the same side of the float, ignoring a negative margin is probably not > so wrong?
I see... This is very interesting. They can't use the term "margin box" since it is the implicit *margin* that "escapes" the float, but then the term "border box" explains this behavior pretty well (at least according to the spec). The problem for us is that this behavior is different across browsers (but what else is new?). -- Regards, Thierry www.tjkdesign.com | articles and tutorials www.ez-css.org | ultra light CSS framework ______________________________________________________________________ css-discuss [cs...@lists.css-discuss.org] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
