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

The Paciello Group comment on SC 3.2.6 - Accidental Activation #330

Closed
patrickhlauke opened this issue Aug 24, 2017 · 3 comments
Closed

Comments

@patrickhlauke
Copy link
Member

(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.

This was referenced Aug 27, 2017
@jasonjgw
Copy link

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.

@DavidMacDonald
Copy link
Contributor

UI components that accept pointer input for activation respond to the release action

OK here's an attempt to incorporate that into the SC

For single pointer activation, at least one of the following is true:

  • activation responds to the release action;
  • A mechanism is available that allows the user to choose activation on the release action as an option;
  • Confirmation is provided, which can dismiss activation;
  • Activation is reversible;
  • non-release activation is essential and waiting for the release would invalidate the activity.

@awkawk
Copy link
Member

awkawk commented Dec 6, 2017

We will add a reference to Pointer Event Spec (https://www.w3.org/TR/pointerevents/#the-pointerup-event) and will add single pointer activation definition change (to "single point")

@awkawk awkawk closed this as completed Dec 6, 2017
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

4 participants