Normalize.css: How about a new version that drops ie9 support?

Created on 3 Apr 2017 · 7Comments · Source: necolas/normalize.css

I would like a normalize edge version that is targeted at all (last two).

Source

ShaggyDude

Most helpful comment

I would argue that if an edge version of normalize were created, to only target browsers that Microsoft itself supports, i.e. IE 11, and latest 2 versions of Edge.

bronzehedwick on 3 Apr 2017

👍5

All 7 comments

I would argue that if an edge version of normalize were created, to only target browsers that Microsoft itself supports, i.e. IE 11, and latest 2 versions of Edge.

bronzehedwick on 3 Apr 2017

👍5

I don't see the benefit of this. As it is, normalize is < 1 kb. Are you really wanting to drop support for IE9 just to spare a few bytes?! Silly idea IMHO.

dagnelies on 10 Apr 2017

I don't understand why for all other browsers 'last two' is generous but IE gets special treatment. Let's push the platform forward and give old browsers an upgrade message.

ShaggyDude on 10 Apr 2017

Let's also be clear. I am suggesting an edge version. One would be free to use the existing version if they work somewhere where they can't upgrade browsers easily (schools).

ShaggyDude on 10 Apr 2017

Internet Explorer is a special use case because it is tied to Windows releases, which limit user upgrade paths.

If one wanted to automate removing those unnecessary bytes for themselves and the rest of the webdev community, they could take advantage of the fact that every part of normalize lists the browsers it targets, which means one could write a PostCSS plugin that omits the rules that do not match a browserslist config.

I’d definitely provide link to such a project in our README.