W3C home > Mailing lists > Public > www-style@w3.org > August 2002

Re: Float overflowing behavior

From: C.Bottelier <c.bottelier@ITsec.nl>
Date: Thu, 15 Aug 2002 12:28:13 +0200
Message-ID: <3D5B823D.45F3376A@ITsec.nl>
To: www-style@w3.org

> >> And yet the real solution is so fantastically
> >> simple?
> >>   <http://css.nu/exp/layer-ex3b.html>
> >>   <http://css.nu/exp/layer-ex3b.html>
> >>   <http://css.nu/exp/layer-ex3d.html>
> 
> >I don't see that as a solution, so much as a hack.
> 
> In my examples (which I have deliberately kept simple and down to
> point) it's a "hack" yes. Never the less it was originally suggested
> directly to me by none the less than Haakon Vium Lie at the time when
> I was doing these "studies" ;-)

If a hack exists or not isn't relevant to the question if a
recommendation
should be extended with a new property or not.

> >While I have seen this in use, and have used it myself in some cases,
> >I don't see it as the proper way for this effect to be accomplished.
> 
> Proper or not; given a web totally polluted with 'text/html' tag soup,
> I can't see this "hack" as really violating anything at all in fact.
> 
> My markup is syntactically correct, as opposed to the vast majority of
> idiocy one can find on the web.

Just because a certain group aren't aware of what they are doing is
wrong
isn't an excuse to say its O.k. Each day many people get murdered so for
this you would find it O.k. to also kill or injure someone? ( I'm aware
this comparison is not on the same scale)

> IMHO I think you are looking at that from the "wrong end" of it.

We're looking at the right end. The end of the how to improve the CSS
recommendation, not the end of the how can we bend the current
recommendations to meet our satisfaction.

> I agree; it would be nice to suggest via CSS that containers are
> supposed to fully enclose their contained elements, even if a
> contained element has been suggested to 'float' (and thus has been
> taken out of the 'flow').
> 
> IMO though; it seems to be more logical if such a property is applied
> to the containing element instead of the contained element.

To my oppinion the element made floating is the right place to add an
attribute because this is the element that has the float attribute that
causes the "to be taken out of flow" behaviour.

Christian
Received on Thursday, 15 August 2002 06:28:25 GMT

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