Ingo Chao wrote:
Big John schrieb:
Combine this with the rules for overflow:auto:
The day I read about this link in Anne's reply to Roger, and all
nodded, I felt like left alone in the dark (not that this is not
common to me).
Nothing to worry about... the theory can be messed up in a dozen ways
just by reading some more from the standards. Not to mention what isn't
written there, and all that is left to the browser-vendors to decide upon.
CSS sure is fun. ;-)
And in praxi:
...see the browsers go crazy :-)
... And a negative margined float will cause a horizontal scrollbar
(:auto) in Moz/Opera by expanding the container horizontally, or is
gone (:hidden) in Opera.
Opera 8 may expand containers to contain floats with a full-height
negative margin-bottom - which it shouldn't (I think). Other browsers
handles that one just fine.
Add in some standard positioning on surrounding elements, and see
Firefox loose stability in positioning and go crazy. Other browsers I've
tested handles those cases just fine.
BTW: responded to another float-containment problem today, and
'overflow:hidden' worked fine in Opera - but sent the whole container
off the page in Firefox. Couldn't find anything about that in the
standards, so I may have to read some more...
Ended up using 'floats to contain floats'.
To me, it's not that super simple.
I agree 100%.
Using 'overflow:auto/hidden' for containing floats is a lot of fun, and
in many cases it'll actually work. However, it is not a reliable
solution, and has to be tested to death across browser-land - in each case.
So, I use it (at my own risk) - but I won't recommend it for anything
but the simplest cases.
regards
Georg
--
http://www.gunlaug.no
______________________________________________________________________
css-discuss [EMAIL PROTECTED]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
