JD_Toims - 11:07 pm on Dec 18, 2013 (gmt 0) [edited by: JD_Toims at 11:16 pm (utc) on Dec 18, 2013]
Which ones exactly that would impact the "average website" aren't supported and how many of those effect anything besides *style* -- I've only been using HTML5 since before it was the recommendation and with the exception of some "advanced" elements [not used on the average site] the only issue I've run into is style, which isn't that difficult to overcome.
The users don't exist for our benefit. We exist for theirs.
Well, imo, it would be to their benefit to update their browser so the web works the way it should and not everyone seems to think they're important enough to keep having 2 [or more] sets of code for. See Below.
For those not wanting to break anything in older browsers, here's a short list of sites/services not quite as concerned about older browsers:
jQuery 2.0 Drops Support for IE6, 7 and 8
Google will drop support for Microsoft's Internet Explorer 7 (IE7) and Mozilla's Firefox 3.5 browsers for its online apps, including Gmail and Docs.
"Beginning August 1, we'll support the current and prior major release of Chrome, Firefox, Internet Explorer and Safari on a rolling basis,"
Google will drop support for Microsoft's Internet Explorer 8 (IE8) for its online apps and services in mid-November, effectively ending support for many users of Windows XP.
Facebook is starting to phase out support for Microsoft Internet Explorer 7 (IE7). First to go is the service's new Timeline profile; when IE7 users visit Facebook profile pages, they don't see the Timeline version, and are instead presented with the old profile design.
Internet Explorer 6, 7 and 8 no longer fully supported
When the Tweet button was introduced in 2010, Microsoft’s Internet Explorer 6 was our baseline. Now, most users have upgraded and we see IE6 usage dwindled. On May 13th 2013, we’re going to prune our support for that browser and its successor, IE7.
[edited by: JD_Toims at 11:16 pm (utc) on Dec 18, 2013]