H1 margin discrepancy between normalize versions.

[JimBobSquarePants]

Due to the removal of margin standardisation in normalize 2.x h1 tags within nested elements will now have an incorrect margin since only the font-size is getting set.

For example, the following markup:

<section>
    <aside>
        <article>
            <h1>heading</h1>
        </article>
    </aside>
</section>

Will be subject to the following selector in Chrome 24.0.1312.52

:-webkit-any(article,aside,nav,section) :-webkit-any(article,aside,nav,section) h1 {
    font-size: 1.17em;
    -webkit-margin-before: 1em;
    -webkit-margin-after: 1em;
}

In version 1.0.2 The margin will be consistent at 0.67em due to the setting of an overall font-size and margin rule for each header tag.

[sjonnet19]

Not to nitpick but i'm seeing the following:

:-webkit-any(article,aside,nav,section) h1 {
    font-size: 1.5em;
    -webkit-margin-before: 0.83em;
    -webkit-margin-after: 0.83em;
}

It shouldn't be an issue since Normalize takes precedence over the user agent stylesheet.

[JimBobSquarePants]

Actually, You are right. I've missed a parent tag in my markup. I'll correct it. As you can see though, this will happen in many scenarios.

As you say normalize would take precedence if there was a rule to overwrite the margin. Without one the margin will be inconsistent and require manual additions to the style sheet each time.

Note. I have seen #74 but I believe this to be an instance where adding the standard margin is necessary.

[sjonnet19]

Sorry I missed you where referring to 2.x.

I actually do add it back in my forked version but for other reasons.

[JimBobSquarePants]

No problem, perhaps I should have been more clear.

[necolas]

Thanks. Fixed.