4 ms·
Why doesnt Mozilla adopt the already widely deployed JavaScript touch API that is already implemented and widespread in Mobile Safari and in the Android Browser
by bni 16y ago
Why doesnt Mozilla adopt the already widely deployed JavaScript touch API that is already implemented and widespread in Mobile Safari and in the Android Browser?
I have used that API a lot lately in my project and it works excellent. The API concept in this Mozilla effort seems exactly the same only different names for everything. NIH syndrome?
- grinich 16y agoThey probably want to do something new and not just try to play catch-up. I'm sure at some point they will be standardized, but with different implementation (and possibly different behavior), it's probably safer to have different APIs for now.
- zmmmmm 16y agoOh, come on, how different can "MozTouchDown" be from "touchstart", "MozTouchMove" from "touchmove", etc? And if they are different isn't that a dick move in itself? It's like Microsoft insisting on its own DOM event apis for no good reason. It achieves nothing, prevents nothing, just acts as a pain in the ass to everyone.
- morroccomole 16y agoI assume the JS Touch APIs are for apple hardware only, or 4% of Firefox users.
- bni 16y agoWrong. There is nothing in a high level JavaScript API that is hardware, or even operating system dependent. Also, as I forgot to mention before, this API is already implemented in Chrome desktop browser.