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 09:28:55 +0200
To: public-webevents@w3.org
Message-ID: <op.vs3gehe03ne1wq@theatreofmagic.local>
On Mon, 28 Mar 2011 18:27:28 +0200, Peter-Paul Koch <pp.koch@gmail.com>  
wrote:

> On 28 March 2011 18:20, Web Events Working Group Issue Tracker
> <sysbot+tracker@w3.org> wrote:
>>
>> WebEvents-ISSUE-9: Interaction of touch events and mouse events [Touch  
>> Events spec]
>>
>> http://www.w3.org/2010/webevents/track/issues/9
>>
>> Raised by: Matt Brubeck
>> On product: Touch Events spec
>>
>> For compatibility with existing web sites, browsers on touchscreen  
>> devices usually translate touch input into mouse events.  Browsers that  
>> support touch events typically send both mouse events and touch events.  
>>  Current implementations allow content to prevent mouse events by  
>> calling preventDefault() on the touch events.
>>
>> To ensure interoperability, Touch Events should specify this behavior.  
>>  For example:
>>
>> * In what order are all the touch events and mouse events sent?
>
> touchstart, touchend, mouseover, mousemove (only one), mousedown,  
> mouseup, click
>
> If the user touches another element the mouseout event of the original
> element fires.
>
> This is the order most of today's browsers actually use. See
> http://quirksmode.org/mobile/tableTouch.html
>

As of version 11, Opera Mobile should follow this touch event order as  
well.

/Anders
Received on Tuesday, 29 March 2011 07:29:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 29 March 2011 07:29:33 GMT