Sent by Arlen Walker on 14 October 2005 22:10
On Oct 14, 2005, at 1:52 PM, Gunlaug Sørtun wrote:
> Arlen Walker wrote:
>
>
>> Love to have someone explain why sometime,...
>>
> FWIW: it's not a browser-bug. It's a part of the W3C CSS2 standard,
> that
> often results in 'complete nonsense'!
> <http://www.w3.org/TR/CSS2/box.html#collapsing-margins>
Hmmm. If the top margin of the h2 is allowed to "reach through" an
unbordered box, but not allowed to reach through a border, you might
be on to something.
If that were the case, the top box (#menu) has no margin specified
but a bottom border specified. The lower box (#overview) has neither,
and the first line is an h2, with the default top margin. That would
mean the top margin of h2 would push down from the #menu bottom
border the default amount, and the #overview box would end up
positioned essentially relative to where the h2's default border
would place it as the top line in the box.
Unfortunately, this idea fails experimentally. I tried putting 1px of
padding at the top of the #overview box. If the above were true, then
the background color would extend 1 pixel higher than before, but not
only does the text move down 1 pixel, but all of the background
reappears. By adding just one pixel, I get about 20 px of background
color.
Have Fun,
Arlen
------------------------------
In God we trust, all others must supply data
______________________________________________________________________
css-discuss [EMAIL-REMOVED]]
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/