Linked by lucas_maximus on Fri 21st Dec 2012 00:09 UTC
Microsoft "In a move that has raised eyebrows, Microsoft has submitted a patch to the WebKit project to extend the open source rendering engine with a prototype implementation of the Pointer Events specification that the company is also working on together with Google, Mozilla, and Opera. WebKit is the rendering engine used in Apple's Safari and Google's Chrome browsers, making Microsoft's work a contribution to products that are in direct competition to its own."
Thread beginning with comment 546067
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: Comment by Drumhellar
by Nelson on Fri 21st Dec 2012 14:14 UTC in reply to "RE[3]: Comment by Drumhellar"
Nelson
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.

Reply Parent Score: 4

BallmerKnowsBest Member since:
2008-06-02

"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.


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.

Reply Parent Score: 7

RE[6]: Comment by Drumhellar
by WorknMan on Fri 21st Dec 2012 20:40 in reply to "RE[5]: Comment by Drumhellar"
WorknMan Member since:
2005-11-13

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 ;)

Reply Parent Score: 7

RE[5]: Comment by Drumhellar
by kristoph on Fri 21st Dec 2012 17:26 in reply to "RE[4]: Comment by Drumhellar"
kristoph Member since:
2006-01-01

I hate to burst your bubble here but it's google who has really driven the adoption of WebKit.

There are way more Chrome (and it's Android ilk) installs out there then there are Safari installs.

]{

Reply Parent Score: 5

RE[5]: Comment by Drumhellar
by pandronic on Fri 21st Dec 2012 17:33 in reply to "RE[4]: Comment by Drumhellar"
pandronic Member since:
2006-05-18

I'm totally uninformed here ... what extensions are you talking about?

Reply Parent Score: 2

RE[6]: Comment by Drumhellar
by Drumhellar on Fri 21st Dec 2012 19:09 in reply to "RE[5]: Comment by Drumhellar"
Drumhellar 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.

Reply Parent Score: 4