- From: Peter-Paul Koch <pp.koch@gmail.com>
- Date: Mon, 28 Mar 2011 18:27:28 +0200
- To: Web Events Working Group WG <public-webevents@w3.org>
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 -- -------------------------------------------- ppk, mobile platform strategist http://quirksmode.org/about/ +.31.6.29585782 --------------------------------------------
Received on Monday, 28 March 2011 16:28:05 UTC