Linked by lucas_maximus on Fri 21st Dec 2012 00:09 UTC
Permalink for comment 546112
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
Linked by Thom Holwerda on 04/16/13 9:29 UTC
More Features »
Sponsored Links



Member since:
2005-07-12
Without getting too specific, there are several extensions that are specific to Apple's browsers that cover things like drawing a beveled edge on an element. Nothing really groundbreaking. Google has their own in Chrome that cover much of the same stuff, and Mozilla has their own in Gecko that cover much the same stuff. Frequently the only difference is the syntax.
These extensions exist generally because they're new features, and the HTML spec hasn't standardized on the specific implementation. However, these aren't meant to be used on production web pages. The problem arises when a site uses them on public-facing pages, and is even worse when they don't put the time in to degrade gracefully, so they tell users that they either "need to upgrade to HTML5" or they just serve a broken page.
Web designers seem to tend to do this more with Safari extensions, but that's merely anecdotal observation on my part.
But, Google did it in a big way with their super-frickin-awesome WebGL star map with WebGL detection code that seemed to not work on my Firefox install.