Well, that's the garbage code that I mentioned. It indicated a deficiency.
The css language isn't allowing us to express what is needed. -Thus a need
for new language, a new property, or new application of an existing one.
It appears as though the w3c started with very simple book-like pages in
mind when the float spec was designed. (Align boxes left or right *within*
paragraphs.) Necessary, but as soon as you stack boxes on top of each other,
e.g., page sections, and use floats within them, the deficiency in css
language becomes apparent. You don't want them bursting their containers.
For now, css can't help as it easily could, so let's change it. That's what
it's there for.
stylo~
-----Original Message-----
From: Jan Roland Eriksson [mailto:jrexon@newsguy.com]
Sent: Wednesday, August 14, 2002 3:37 PM
To: www-style@w3.org
Cc: stylo~
Subject: Re: Float overflowing behavior
On Tue, 13 Aug 2002 12:42:54 -0400 (EDT), you wrote:
[...]
>Floats busting out of their containers, overlapping their container's
>borders, and interfering with subsequent sections is not only
>counterintuitive, but a continual headache that makes the use of floats a
>nightmare. I hear this repeatedly on developer boards/lists. Normally you
>have sections, often with borders, and floated divs/images within them that
>you quite rightly want to remain within them. The w3c pic
>http://www.w3.org/TR/CSS2/images/float2p.gif demonstrates exactly what is
>NOT wanted 99% of the time, and what developers are continually asking for
>workarounds to. -And what is forcing them to maintain table layouts and the
>align attribute.
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>
There is no need to make a hen of a single feather.
--
Rex