3 ms·
I think you've reached a slightly perverse conclusion. From the source: >Pointer events would likely never supplant touch events on the web (especially withou
by andybak 12y ago
I think you've reached a slightly perverse conclusion.
From the source:
>Pointer events would likely never supplant touch events on the web (especially without support from Safari). Since touch events are here to stay, supporting another largely redundant input model has a high long-term complexity cost on the web platform.
Sounds to me like the Blink time is trying to use their say to reduce fragmentation and they've taken the side of practicality. Rough consensus and running code indeed.
The other points seem equally sensible to me (at least at first glance) - and a long way from "ignoring each other as much as possible while pursuing their own improvements"
- fidotron 12y agoThe Blink team have simply become the new IE style refuseniks, using mobile performance as the standard excuse. Mozilla, Apple and Microsoft have all been creating new "standard" APIs which no one else implements, yet in order to get best performance on their systems you have to use. 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.
- teleclimber 12y ago> 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.
- gtjrossi 12y agoOn 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-skype-like-chat-on-the-web/ http://www.cnet.com/news/reconciliation-draws-closer-for-sky... For IE implementation status, follow along here: http://status.modern.ie/webrtcobjectrtcapi http://status.modern.ie/webrtcobjectrtcapi and check out our ORTC prototype: http://html5labs.interoperabilitybridges.com/prototypes/object-rtc/object-rtc/info http://html5labs.interoperabilitybridges.com/prototypes/obje...
- cromwellian 12y agoYou 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.