Re: [w3c/uievents] Add WheelEvent#wheelDelta/wheelDeltaX/wheelDeltaY (#138)

> Does content depend on these attributes behaving differently in Chrome, Edge and Safari, and do they actually?

I don't know, but in my experience, most web apps which handle wheel event directly have bugs with various situations. For example, not supporting high resolution scroll, not supporting page scroll.

> If those three are well enough aligned, are there additional compat constraints that Gecko would run into if trying to add them?

It's difficult to say now. The attributes are designed before high resolution scroll, so, I'm not sure if these values can make sense even with modern devices.

The meaning of these attributes are really different in physical or logical level:

IE (I don't know about Edge's behavior), Chrome for Windows, Chrome for Linux, Chrome for macOS with non-continuous wheel device indicate physical amount of turned distance.

On the other hand, Chrome for macOS with continuous wheel device and Safari indicate computed scroll amount which is computed with acceleration, etc.

-- 
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/138#issuecomment-285261522