You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 30, 2018. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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.
(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.
The European team STF536 discussed 2.1.1 and suggested adding some words to read:
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.
The text was updated successfully, but these errors were encountered: