On Android at least, we don't seem to have this same mutually exclusive gesture/touches problem. We receive touches in our Native UI layer, send them to Gecko, and use Native gesture detectors at the same time. That code is in a bit of flux at the moment as we're merging our Asynchronous Pan-Zoom code with B2G's (which is in turn, basically a C++ implementation of our code), while still using native gesture detectors (in some places). We also asynchronously fire nsIDOMSimpleGestureEvents for pinchzoom events (but not for any swipes). Because there's no exclusivity between determining gestures and touches, we fire touch events whether or not preventDefault() was called on the first touchstart/move of a series.
Mouse emulation is also done via native gesture detectors (detecting taps and double taps and sending message to our javascript frontend). It would be nice to move that into the platform to ensure its done consistently across platforms. I haven't really looked at the new AsyncPanZoom stuff, but I was hoping it would provide a path forward to make that happen. Someone who knows that code better should comment, but I assume it should also replace the Metro javascript pan/zoom stuff at some point, perhaps backed by native gesture detection when the page doesn't have touch handlers, and using b2g's gesture detection at other times? Maybe that's orthogonal to this problem... - Wes ----- Original Message ----- From: "Justin Dolske" <dol...@mozilla.com> To: dev-platform@lists.mozilla.org Sent: Sunday, April 21, 2013 7:01:07 PM Subject: Re: Revamping touch input on Windows On 4/18/13 5:50 AM, Jim Mathies wrote: > One of the concerns here is that since we do not differentiate the metro > and desktop browsers via UA, the two should emulate each other closely. > The browser would appear completely broken to content if the same UA > sent two different event streams. So we need to take into account how > metrofx works as well. How does the current/proposed state of affairs compare to other platforms (notably OS X and Android)? While the Metro-vs-Win8 case seems especially important to get right (since the same user on the same device may commonly flip between both), I'd hope web authors can write/test for on one platform and be reasonable able to expect their code to work the same everywhere. It's not clear to me how that ties in with what you're talking about. Justin _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
