See [wheelDelta value of Chrome](https://developer.mozilla.org/en-US/docs/Web/Events/mousewheel#Chrome). Even if we follow Chrome's spec, the behavior does not make sense (although I don't check the latest behavior of Chrome). Currently, I'm investigating what we can do for bug 1406243. One possible idea is, start to dispatch `DOMMouseScroll` with `0` for `detail` even in the cases we dispatch only `MozMousePixelScroll`.
Bug 1529953 Comment 1 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
See [wheelDelta value of Chrome](https://developer.mozilla.org/en-US/docs/Web/Events/mousewheel#Chrome). Even if we follow Chrome's spec, the behavior does not make sense (although I don't check the latest behavior of Chrome). Currently, I'm investigating what we can do for bug 1406243. One possible idea is, start to dispatch `DOMMouseScroll` with `0` for `detail` even in the cases we dispatch only `MozMousePixelScroll`. But if there are web apps which do like the following, it breaks the web apps anyway: ``` foo.addEventListener("DOMMouseScroll", (event) => { if (event.detail > 0) { // Do something for scroll to bottom event. return; } // Do something for scroll to up event. }); ``` So, `0` may be handled as scroll down or up.