Re:Blink won’t implement pointer events
by teleclimber on Friday August 15, 2014 @12:55PM
(#8183043)
> The Blink team have simply become the new IE style refuseniks
Don't kid yourself. Sometimes it's the IE team that refuses to play along. Example: WebRTC.
Overall I feel that the cooperation between vendors on standards is quite good. but you can't expect all these mega corps to agree on everything all the time.
On the contrary! I work on the IE team and we're playing along nicely. Google just joined us on the ORTC spec, which Chrome considers to be essentially Web RTC 1.1.
http://www.cnet.com/news/reconciliation-draws-closer-for-sky...
For IE implementation status, follow along here: http://status.modern.ie/webrtcobjectrtcapi
and check out our ORTC prototype: http://html5labs.interoperabilitybridges.com/prototypes/obje...
Re:Blink won’t implement pointer events
by cromwellian on Sunday August 17, 2014 @04:03AM
(#8188908)
You mean like Apple refusing Pointer Events first, or Mozilla refusing WebP, NaCL/PNaCl/Pepper, trying to refuse Web Audio, MS refusing WebGL, Canvas, Web Audio, WebRTC.
Every vendor fights their own turf battles. Not-invented-here seems to also be a big issue in standards committees.
If you read the history of that bug someone rightly points out a key thing is MS have to support the pen on surface, and that was as important to MS there as multitouch was to Apple with iOS. Mobile performance is clearly that to the Chrome team, and this mismatch of priorities is what is at the root of the problem.