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

Here's my recollection of the state in various browsers.  @sahel-sh can you fill in details / provide a test case please?

- In Chrome non-passive wheel events are always cancelable and synchronous, a big problem for scroll performance. Your change proposes making only the first wheel in a touchpad gesture cancelable.
- Edge doesn't fire wheel events at all for touchpads due to this perf issue.  I talked with @toddreif and @scottlow at TPAC.  At the moment they're looking to send touchscreen pointer events for touchpad scrolling, but admitted it wouldn't fix all the web compat problems with their lack of wheel support and so sounded intrigued by this proposal.
- Firefox makes some wheel events async to avoid this problem, but they're still cancelable with some complex after-the-fact behavior (@staktrace)
- Safari - can be async, right?  I'm not sure of the details myself.

-- 
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-343685510