From d0cc7698e7a4338a825088ea029abd5beb1f960e Mon Sep 17 00:00:00 2001
From: "Patrick H. Lauke"
- The user agent may dispatch both touch events and mouse events
+ The user agent may dispatch both touch events and (for compatibility with web content not designed for touch) mouse events
[[!DOM-LEVEL-2-EVENTS]] in response to the same user input. If the
user agent dispatches both touch events and mouse events in response to
a single user action, then the Extensions to the
GlobalEventHandlers
interfaceInteraction with Mouse Events and
click
touchstart
event type must be
dispatched before any mouse event types for that action.
If touchstart
, touchmove
, or touchend
are canceled, the user agent should not dispatch any mouse
- event that would be a consequential result of the the prevented touch
+ event that would be a consequential result of the prevented touch
event.
Interaction with Mouse Events and
click
- User agents will typically dispatch mouse and click events when there is only a single - active touch point. Multi-touch interactions – involving two or more + User agents will typically dispatch mouse and click events only for single-finger activation gestures (like tap and long press). Gestures involving movement of the touch point or multi-touch interactions – with two or more active touch points – will usually only generate touch events.
- If the user agent interprets a sequence of touch events as a click,
+ If the user agent interprets a sequence of touch events as a tap gesture,
then it should dispatch mousemove
, mousedown
,
mouseup
, and click
events (in that order) at the location
of the touchend
event for the corresponding touch input. If the