Re: [w3c/uievents] Expose wheel event scrolling state to DOM events (#170)

> Firefox makes latter wheel events async to avoid this problem, but they're still cancelable with 
> some complex after-the-fact interruption behavior (@staktrace). It's not clear to me there are use 
> cases which really justify this strange "after-the-fact interruption" behavior.

Yeah, the behaviour is basically, "if content does preventDefault on a wheel event later in the transaction, then try to stop the scrolling ASAP and start a new transaction". It can result in non-deterministic behaviour, and we didn't really have specific use cases that drove this behaviour, it was more so just trying to get as much async scrolling as we could while still leaving an escape hatch for content to stop it in some theoretical cases. It may be that we don't need this complexity and can just treat those wheel events as non-cancelable.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/uievents/issues/170#issuecomment-343963049