Re: [w3c/uievents] Specify wheel event groups (PR #344)

@garykac commented on this pull request.



> @@ -2180,11 +2180,12 @@ myDiv.addEventListener("auxclick", function(e) {
    +| Sync / Async     | Async                                                                                |
    +| Bubbles          | Yes                                                                                  |
    +| Trusted Targets  | <code>Element</code>                                                                 |
-   +| Cancelable       | <a href="#cancelability-of-wheel-events">Varies</a>                                                  |
+   +| Cancelable       | <a href="#cancelability-of-wheel-events">Varies</a>                                  |
    +| Composed         | Yes                                                                                  |

I assume that this change was not intentional.

> @@ -381,6 +381,12 @@ the definitions for more information.
  the [[#conf-interactive-ua]] and [[#conf-author-tools]] for details on the
  requirements for a <em>conforming</em> user agent.
 
+: <dfn>wheel event group</dfn>

We're moving away from having entries in glossary since they are not normative and mostly duplicate definitions that are properly defined elsewhere.

I think this should just be included up with the rest of the text.

> @@ -2236,6 +2237,19 @@ myDiv.addEventListener("auxclick", function(e) {
    EVENT{wheel} event with multiple non-zero axes or as separate
    EVENT{wheel} events for each non-zero axis.
 
+   A <a>user agent</a> SHOULD create a wheel event group when the first
+   wheel event is fired, so that all subsequent wheel events within a
+   implementation-specific amount of time can be targetted at the same
+   element.
+
+   <p class="example">
+   If a series of wheel events targetted in a scrollable element start
+   above a child element, later events for the same user gesture may
+   occur over the child element. In the case that {{Event/preventDefault()}}
+   is called in a wheel event handler for the child element, targetting
+   the child element could result in unexpected behavior for the user.
+   </p>

I think having examples can be really useful.

I'm not sure what the takeaway is for this example, though. It ends with "could result in unexpected behavior", which makes it sound like a cautionary tale. Is this trying to explain why it is spec'ed this way, or is there something that the user needs to do to avoid the unexpected behavior?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/uievents/pull/344#pullrequestreview-1419432902
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/uievents/pull/344/review/1419432902@github.com>