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

Re: Float overflowing behavior

From: Vadim Plessky <lucy-ples@mtu-net.ru>
Date: Fri, 16 Aug 2002 12:03:54 +0400
To: "C.Bottelier" <c.bottelier@ITsec.nl>, www-style@w3.org
Message-Id: <200208161203.54335.lucy-ples@mtu-net.ru>

On Thursday 15 August 2002 2:28 pm, C.Bottelier wrote:
|  > >> 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.

Jan Roland's code is Valid HTML and Valid CSS, you can't call this wrong!
If you want to see bad code - go to Microsft or AOL Time Warner web sites, you 
will have *enough* of _hacks_ there!

|
|  > >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)

so, *what* is your proposal?
You are going to fix 'float', right?
Than please read archives for this mailing list first.
In particular, "Re: How is it possible to devise such a feeble system?" 
discussion thread, from October 2001.

There is nothing new in the fact that CSS is not easy to use (comparing to, 
say, typical DTP system and its paradigms) and was designed not in a best 
way.
But due to the need of backward compatibility, this can't be changed 
dramatically. Just slightly enhanced :-)

|
|  > 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.

Than you need to design another specification!
Or, may be, SVG will better suit your needs.

|
|  > 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

Best Regards,
-- 

Vadim Plessky
http://kde2.newmail.ru  (English)
33 Window Decorations and 6 Widget Styles for KDE
http://kde2.newmail.ru/kde_themes.html
KDE mini-Themes
http://kde2.newmail.ru/themes/
Received on Friday, 16 August 2002 03:57:40 GMT

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