W3C home > Mailing lists > Public > public-webevents@w3.org > January to March 2011

Re: WebEvents-ISSUE-9: Interaction of touch events and mouse events [Touch Events spec]

From: Anders Höckersten <andersh@opera.com>
Date: Tue, 29 Mar 2011 10:39:17 +0200
To: public-webevents@w3.org
Message-ID: <op.vs3jnrge3ne1wq@theatreofmagic.local>
On Mon, 28 Mar 2011 18:44:07 +0200, Matt Brubeck <mbrubeck@mozilla.com>  
wrote:

> There is a related issue on browsers that support both touch and mouse  
> input - for example, Firefox 4 on Windows 7 tablets.
>
> On platforms like Windows, the operating system may translate touch  
> input into mouse movements.  This means that, instead of one "mousemove"  
> event happening after the "touchend" event, mousemove events and  
> touchmove events are interleaved.  (Maybe these mouse events should be  
> suppressed if preventDefault() is called on one or more of the touch  
> events?)
>
> [removed text Matt left in by mistake]
>
> I'm not yet clear enough about this problem to enter any issues in  
> Track, but I'd like to hear other thoughts.

I can add that QT also has this behavior of sending both mouse events and  
touch events, at least on some systems[1].

I'm leaning towards wanting to ignore system mouse events that are  
generated for touch events, and let the browser handle emulation of mouse  
events by itself. The reason is that I don't see why website makers should  
have to worry about the specific touch/mouse behavior of different OSes  
(beyond having to cater to both touch and mouse separately, of course),  
but perhaps I'm missing something here?

/Anders

[1]  
http://doc.trolltech.com/latest/qtouchevent.html#mouse-events-and-the-primary-touch-point
Received on Tuesday, 29 March 2011 08:39:51 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 29 March 2011 08:39:53 GMT