Expand mouse/click interactions #65
Conversation
patrickhlauke
commented
Apr 22, 2016
patrickhlauke
commented
- introduce the concept of "compatibility" mouse events (to explain why UAs may choose to fire both touch and mouse/click)
- remove stray "the"
- expand note about when UAs typically don't fire mouse events+click - not just mutli-touch, but also any gestures that aren't a tap
- optimistically replace "click" with "activation/tap gesture", hoping lawers won't swoop down on it
|
the third bullet addresses #63 |
| @@ -895,13 +895,13 @@ <h3 id="event-touchcancel">The <dfn class="event"><code>touchcancel</code></dfn> | |||
| </p> | |||
|
|
|||
| <p class="note"> | |||
| User agents will typically dispatch mouse and click events when there is only a single | |||
| <a>active touch point</a>. Multi-touch interactions – involving two or more | |||
| User agents will typically dispatch mouse and click events only for an activation/tap gesture, and only when there is a single | |||
There was a problem hiding this comment.
Most UAs send mouse events / contextmenu for a long press gesture too, right?
|
Looks good generally though we probably need to relax this slightly to handle long press or other |
|
would just saying "tap gesture" rather than "activation/tap gesture" be sufficiently vague to cover |
|
Not in chromium's gesture terminology, no ("tap" and "long press" are entirely different gestures). You could say "single finger stationary gestures" to include them both. Or even just call them out explicitly, eg, "single finger activation gestures (like tap and long press)". I agree "typically" is enough to let us ignore the niche cases like "two finger tap". |
liking that...will make a change and force-push result |
|
done |
| @@ -895,13 +895,13 @@ <h3 id="event-touchcancel">The <dfn class="event"><code>touchcancel</code></dfn> | |||
| </p> | |||
|
|
|||
| <p class="note"> | |||
| User agents will typically dispatch mouse and click events when there is only a single | |||
| <a>active touch point</a>. 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), and only when there is a single | |||
There was a problem hiding this comment.
nit: the "and only when..." is now redundant with "single finger", right? Could just remove the 2nd part entirely?
Also should "single finger" be hyphenated?
|
@RByers right on both comments. fixed. |
|
LGTM, thanks! |
