Skip to content
This repository has been archived by the owner on Jun 30, 2018. It is now read-only.

Additional words for 2.5.1 Pointer Gestures #663

Closed
mapluke opened this issue Jan 8, 2018 · 1 comment
Closed

Additional words for 2.5.1 Pointer Gestures #663

mapluke opened this issue Jan 8, 2018 · 1 comment

Comments

@mapluke
Copy link

mapluke commented Jan 8, 2018

The European team STF536 discussed 2.1.1 and suggested adding some words to read:

All functionality which uses multipoint or path-based gestures for operation can be operated with a single pointer @@without a path-based gesture@@, unless a multipoint or path-based gesture is essential.

Rationale: Since the statement says “OR path based” -- this applies to multipoint and (single point) path based gestures. So this should say that the solution is not multipoint and not path based -- unless either or both is essential.

@detlevhfischer detlevhfischer self-assigned this Jan 9, 2018
detlevhfischer added a commit that referenced this issue Jan 9, 2018
also changed "single-point activation" to "single pointer" because "single-point activation" clould be understood to exclude double click and double tap. Not sure which was the more recent phrasing.
@awkawk awkawk changed the title Additional words for 2.1.1 Pointer Gestures Additional words for 2.5.1 Pointer Gestures Jan 9, 2018
@awkawk
Copy link
Member

awkawk commented Jan 21, 2018

(Official WG response)
Thank you for your suggestion. We agree that your addition clarifies the text of SC 2.5.1 Pointer gestures. Path-based gestures are often carried out with a single pointer (as in drag-and-drop) so including an explicit reference ("...can be operated with a single pointer without a path-based gesture") leaves less room for misunderstanding.

@awkawk awkawk closed this as completed Jan 21, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants