Normalize v2.0.1 - optimized for modern browsers(necolas.github.com) |
Normalize v2.0.1 - optimized for modern browsers(necolas.github.com) |
Also, I reckon test case examples for each browser quirk would be cool, so people who wanna see what each thing changes/causes, can go through the commented code and see what removing certain declarations would change/effect.
Keep developing cool stuff necolas!
There is accommodating customers, usually large organisations, who for whatever reason have chosen stability in their system software. And then there is not taking advantage of new technologies that almost everyone in most markets can use, and that almost everyone else could upgrade to if they needed to, just to support a tiny and shrinking minority.
If you still need legacy browser support, then use 1.x.
I "dropped" IE8 support in 2010: http://impactjs.com/
Hard to tell which mini-comments are needed for hacks or not.
IE8 makes up 11.9%, so we do proper testing there, and the content should look as close as possible to modern browsers, but I'm happy to include polyfills etc where needed.
For us, Chrome is 21.1%, Mobile Safari is 17.5%, IE9 is 17.1%, and Firefox is 15.6%, so for us over 70% of users have a modern browser. These 4 are our target browsers, where everything should work.
As a concession to old browser users, I will use XHTML or an older spec on a site that has large IE<9 usage. But I'm sure as hell not going to spend a lot of time debugging and fluffing the pages anymore. These people don't care enough about the Internet to not use IE7 or 8, then I don't care if their experience is sub par.