The other thing that occurred to me is that the <TABLE> inside of my DIV
is _one_ element.
I'm betting that CSS the browser isn't capable of splitting up <TR>
elements just to meet some containing block width requirement.
I think that that is my problem.
Wes
Gunlaug Sørtun wrote:
>Wes Gamble wrote:
>
>
>>If there is a table inside of it that is wider than the 63% of the
>>body tag that I've given it, the entire main DIV stretches to
>>accomodate it and overlaps the "right_status" DIV.
>>
>>
>
>That sounds like IE/win behavior: "auto expanding", which is a genuine
>bug in that browser. Other browsers will do less buggy, but maybe just
>as nasty-looking things when we try to plug a "too wide" element into a
>"too narrow" container.
>
>Adding...
>
>#main {overflow: auto;}
>
>...is the general solution that will work in all browsers.
>
>
>
>
>>I'm floating each of those boxes so that I can retain their block
>>element nature - however, this feels like cheating since I don't
>>really need to float anything. I'm only floating the divs because
>>when I tried to use "display: inline;" to put the DIVs next to each
>>other, I ran into a lot of problems. Is there a better way to lay
>>this out in general?).
>>
>>
>
>Floating boxes (containers) to make them line up side by side, is the
>most used method. You may see it as cheating, but there aren't all that
>many proper and well-working methods around.
>The more elegant solution: CSS tables[1], isn't supported by IE/win, so
>no go there.
>
>regards
> Georg
>
>[1]http://www.w3.org/TR/CSS21/tables.html
>
>
______________________________________________________________________
css-discuss [EMAIL PROTECTED]
http://www.css-discuss.org/mailman/listinfo/css-d
IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7
List wiki/FAQ -- http://css-discuss.incutio.com/
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
