Remove more outdated styles

[sindresorhus]

Remove more outdated styles

[charakterziffer]

I’m pretty sure the smaller h1 is a feature, not a bug. Since HTML5 it’s possible, to ignore the “correct” header nesting, use only h1 and signal the subordination with nested sections or articles, see https://stackoverflow.com/questions/24986162/html5-nested-sections-and-heading-tags/24987792#24987792

Yes, browser may interpret this different, but if you resize the nested h1 back to it’s original size you prevent this possibility HTML5 offers. It would be more correct to enable this smaller sectioned headings in all browsers (IE 6/7, too), but because it depends heavily on the whole context, that may be difficult to do with normalize.css.

[ismamz]

Hi @sindresorhus! Are you just testing in the last version of Chrome and the last version of Firefox?

[sindresorhus]

Yes

[ismamz]

The h1 element has the same behavior in both browsers (within article or section too). So, the rule here it should not be necessary if you are "normalizing", otherwise it should be indicated as "opinionated".
Are you agree?

[sindresorhus]

@ismamz Try using git blame to see when it was introduced and why. There might be something you're missing. https://github.com/necolas/normalize.css/blame/master/normalize.css

[ismamz]

@sindresorhus Sorry, but I don't find the reason to keep this rule. Maybe I missing something. I did a test and there are no difference when you write h1 within nested HTML sections (section, aside, etc). By the way, a HTML test file could be useful.

[sindresorhus]

Sorry, but I don't find the reason to keep this rule.

That's why I'm asking you to dig into why it was added in the first place. Even if you can't reproduce it, doesn't mean it's not there for a good reason. I'm not saying this is the case here, but we should always dig into the origins to find out. These are the relevant commits: necolas/normalize.css@e9e2874 necolas/normalize.css@fc85cfb

[ismamz]

@charakterziffer I agree that it is a feature. How modern-normalize does not support IE and other older browsers that might have trouble with this, there is no need to support them. There is no reason to keep it in modern-normalize.css (it does not normalize), and perhaps it can be useful in modern-base.css.

Here is a related issue: #23