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
ty easily I would think.
Jim
-Original Message-
From: Justin Dolske
Sent: Sunday, April 21, 2013 9:01 PM Newsgroups: mozilla.dev.platform
To: dev-platform@lists.mozilla.org
Subject: Re: Revamping touch input on Windows
On 4/18/13 5:50 AM, Jim Mathies wrote:
One of the concerns here is that
From: "Justin Dolske"
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
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 nee
I work on touch support in Chrome desktop (and the touch events and pointer
events standards). Most of the mozilla implementation details in this thread
are over my head, but I wanted to add a couple comments in case it's helpful.
Inline.
On Thursday, April 18, 2013 10:06:57 PM UTC-4, Tim Abr
On 04/18/2013 03:50 PM, Jim Mathies wrote:
We have quite a few issues with touch enabled sites on Windows. [1] Our support
for touch stretches back to when we first implemented MozTouch events
which over time has morphed into a weird combination of W3C touch / simple
gestures support. It is rat
>> The metro/WinRT widget backend can take advantage of native gesture
>> recognition, so maybe in the future we would want to implement the
>> ability to opt-out of front-end gesture recognition. I don't think we
>> should do this in the immediate term, but as backends get better and
>> better nat
"Tim Abraldes" wrote in message
news:...
> > 1) abandon generating nsIDOMSimpleGestureEvents on Windows for both
> backends
> > when processing touch input from touch input displays.*
> >
> > This would mean that if the desktop front end wants to do something with
> > pinch or zoom, it would have
> 1) abandon generating nsIDOMSimpleGestureEvents on Windows for both
backends
> when processing touch input from touch input displays.*
>
> This would mean that if the desktop front end wants to do something with
> pinch or zoom, it would have to process W3C touch events instead. Note
that
> we co
We have quite a few issues with touch enabled sites on Windows. [1] Our
support for touch stretches back to when we first implemented MozTouch
events which over time has morphed into a weird combination of W3C touch /
simple gestures support. It is rather messy to fix, but I'd like to get this
10 matches
Mail list logo
