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.
(rather than necro-posting on closed issues, posting these as new - albeit late - issues)
We feel that the normative SC text here is far too tech-specific, despite the attempt to use more generic/made-up names like "up-event". The SC text should really be "ensure that users do not accidentally activate...". Then, in the understanding document, elaborate about common situations where accidental activation can happen, e.g. on touchscreen, if scripting reacts to the finger being placed on the screen (the "down-event", i.e. "touchstart" or "pointerdown"), this will result in accidental triggering, and that the simplest remedy here is to react to the "up-event" (i.e. "touchend" or "pointerup"). The same for mouse interactions (reacting to "mouseup" or indeed "click" rather than "mousedown"). Then mention alternatives where users can potentially set this via configuration/settings.
The text was updated successfully, but these errors were encountered:
I don't think content authors can ensure that UI components are not accidentally activated. Thus, it seems to me that "ensure that users do not ..." or similar formulations are not reliably testable.
However, it would be possible to state the current requirement more generally (e.g., UI components that accept pointer input for activation respond to the release action). This doesn't refer to specific events, yet more accurately describes what is intended.
(rather than necro-posting on closed issues, posting these as new - albeit late - issues)
We feel that the normative SC text here is far too tech-specific, despite the attempt to use more generic/made-up names like "up-event". The SC text should really be "ensure that users do not accidentally activate...". Then, in the understanding document, elaborate about common situations where accidental activation can happen, e.g. on touchscreen, if scripting reacts to the finger being placed on the screen (the "down-event", i.e. "touchstart" or "pointerdown"), this will result in accidental triggering, and that the simplest remedy here is to react to the "up-event" (i.e. "touchend" or "pointerup"). The same for mouse interactions (reacting to "mouseup" or indeed "click" rather than "mousedown"). Then mention alternatives where users can potentially set this via configuration/settings.
The text was updated successfully, but these errors were encountered: