I wanted to share this article I found that helped me understand the concepts:
http://reference.sitepoint.com/css/collapsingmargins . It has some good
examples too.
>
> > This is a very special case of margin-collapsing in that the affected > div
>has a min-height specified. As I noted in my
What I don't understand is why there is collapsing margins at all. What is the
rationale?
>-Original Message-
>From: css-d-boun...@lists.css-discuss.org [mailto:css-d-boun...@lists.css-
>discuss.org] On Behalf Of Philippe Wittenbergh
>Sent: Thursday, August 09, 2012 4:51 AM
>To: CSS-D
>C
Philippe Wittenbergh wrote:
Back in time – somewhere in 2007 or so – when we first discussed and
investigated this, the Gecko behavior was correct. But the spec text
was different. Since then, the CSS WG discussed that issue and
modified the spec text (quoted below); see the links provided by
Le 9 août 2012 à 20:06, Philip TAYLOR a écrit :
> But what for behaviour does the specification call, Philippe, in
> your opinion ?
Back in time – somewhere in 2007 or so – when we first discussed and
investigated this, the Gecko behavior was correct. But the spec text was
different. Since the
Philippe Wittenbergh wrote:
> This is a very special case of margin-collapsing in that the affected
> div has a min-height specified. As I noted in my first reply, this
> calls for a more complex behaviour. And it is in this very special
> case that browsers don't really agree on what to do wit
On 9/08/2012 8:58 AM, Philippe Wittenbergh wrote:
Le 9 août 2012 à 03:41, David Hucklesby a écrit :
Well, this article explains this in terms of a top margin. Bottom margins
behave the same way--but not in all browsers, it seems.
I admit that this continues to confuse me, too, as the behavior