Fw: Revamping touch input on Windows

2013-04-22 Thread Jim Mathies
-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 since we do not differentiate

Re: Revamping touch input on Windows

2013-04-21 Thread Justin Dolske
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

Re: Revamping touch input on Windows

2013-04-20 Thread rbyers
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

Re: Revamping touch input on Windows

2013-04-19 Thread smaug
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

Re: Revamping touch input on Windows

2013-04-18 Thread Tim Abraldes
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 could

Re: Revamping touch input on Windows

2013-04-18 Thread Jim Mathies
Tim Abraldes tabral...@mozilla.com wrote in message news:aamdndrkq8yrr-3mnz2dnuvz_hwdn...@mozilla.org... 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

Re: Revamping touch input on Windows

2013-04-18 Thread Tim Abraldes
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 native