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
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
A path-based gesture involves an interaction where not just the endpoints matter, but how the pointer moves between these points.
If the gesture is only recognised if the user moves in a (mostly) straight line from the start point to the end point, it is an example of a path-based gesture.
That second sentence is confusing. It is an example of a common characteristic of some path-based gestures. I propose replacing it with:
Swiping is an example of a path-based gesture which is only recognized when the user moves in a (mostly) straight line from the start point to the end point.
Under Intent, we currently have:
> A **path-based gesture** involves an interaction where not just the endpoints matter, but how the pointer moves between these points.
>
> If the gesture is only recognised if the user moves in a (mostly) straight line from the start point to the end point, it is an example of a path-based gesture.
That second sentence is confusing. It is an example of a common characteristic of some path-based gestures.
First example of path-based gesture
If the gesture is only recognised if the user moves in a (mostly) straight line from the start point to the end point, it is an example of a path-based gesture.
FWIW, this came up in the context of WCAG 3 complex pointer inputs drafting. We were looking for a definition of simple pointer inputs. We used single-pointer as part of our draft glossary when we noticed single pointer input is currently just a place-holder with the WCAG 3 editors draft.
We used single-pointer as part of our draft glossary when we noticed single pointer input is currently just a place-holder with the WCAG 3 editors draft.
incidentally, I'm glad to see that WCAG 3 is defining the proper "single pointer input" rather than just "single pointer" ... this had been a blunder in WCAG 2 at the time (which is what caused the various contortions to address this/clarify this somehow - #3536 and #4070)
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Under Intent, we currently have:
That second sentence is confusing. It is an example of a common characteristic of some path-based gestures. I propose replacing it with: