From what I've heard Microsoft's PointerEvents offer a better complete model, without creating a web-standard which involves risks of getting sued by Apple should you ever dare to implement it.
For once, it seems Microsoft has a better option.
And no, just because it's in WebKit doesn't make it better, much less an official standard. WebKit is the new IE and it's destructive for the web. People design for "Webkit" as if it was the standard, and expect everyone else "to eventually come along". We did see how well that plays out not that many years ago, but then we did it for MSIE.
As a 5 minute user of Firefox mobile, I can attest to this happening right now. The mobile web is at this point not even usuable on a non-webkit browser.
This is bad for the web. You are doing it. Please stop doing it.
The only thing good for the web is following web-standards. If you're not complying to them, you are doing something wrong, and I don't care what your reason is: You are doing something wrong.
> For once, it seems Microsoft has a better option.
Not for the first time. * { box-sizing: border-box; } is a staple of mine.
> WebKit is the new IE and it's destructive for the web.
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. ... The first specification, Touch Events, has been essentially abandoned.[1]
> The mobile web is at this point not even usuable on a non-webkit browser. This is bad for the web. You are doing it. Please stop doing it.
There's no need to hector web developers about this. (I assume that's what you meant by 'you'.) It's mostly up to the browser makers to hash this out. Microsoft's contribution to Webkit was an exemplary and, from what I can see, much-welcomed response to Apple's patent shenanigans over Touch. Let's just give it time.
It's worth bearing in mind that Android (which ships Webkit by default) is currently the only mainstream mobile OS that even allows unrestricted use of independent browser technology, which is partly why Firefox Mobile is only available for that platform.
I'm not only partial to TouchEvents because they're better supported across browsers. IE makes you handle all the pointers independently, which is great for toy demos of drawing apps, but really cumbersome for actually implementing gestures with compared to simply iterating over TouchEvent.targetTouches.
For once, it seems Microsoft has a better option.
And no, just because it's in WebKit doesn't make it better, much less an official standard. WebKit is the new IE and it's destructive for the web. People design for "Webkit" as if it was the standard, and expect everyone else "to eventually come along". We did see how well that plays out not that many years ago, but then we did it for MSIE.
As a 5 minute user of Firefox mobile, I can attest to this happening right now. The mobile web is at this point not even usuable on a non-webkit browser.
This is bad for the web. You are doing it. Please stop doing it.
The only thing good for the web is following web-standards. If you're not complying to them, you are doing something wrong, and I don't care what your reason is: You are doing something wrong.