To view parent comment, click here.
To read all comments associated with this story, please click here.
And this is exactly how Apple has turned WebKit into the IE6 of the Mobile Web using their proprietary vendor extensions (and then refusing to work with Mozilla and MSFT or the W3C on Pointer Events spec).
I guess this is what people want.
And even better, there hasn't been a single peep about that from the iFanboys who rambled on about how Apple's crusade against Flash was purely for the greater good of web standards. I guess that, in their minds, it's A-OK when Apple willfully ignores and undermines established standards - but the same behavior is unacceptable from any other company.
Haven't you heard? Everything is Magical when Apple does it
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.





Member since:
2005-11-29
"Standardised on WebKit" is the most ridiculous thing I've heard today. Thanks for the laugh.
And this is exactly how Apple has turned WebKit into the IE6 of the Mobile Web using their proprietary vendor extensions (and then refusing to work with Mozilla and MSFT or the W3C on Pointer Events spec).
I guess this is what people want.