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

@dlrobertson commented on this pull request.

Thanks for the feedback!

> @@ -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 my goal was "to explain why it is spec'ed this way". Is something like that typical in a spec or just contained to the spec issue and PR? This is also something that is easier to see with an actual example with a scrollable frame with a subframe that preventDefault's wheel events

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

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