I just don’t know where to fill out a ticket about a bug as a user.
So, let me describe it here:
If user uses zoom option (cmd+opt+8), and trying to scroll some window with mouse - it uses incorrect pointer position for scrolling events.
The easiest way to check it - just open any browser on some long page with scrollers (I use the results page on the google search engine for some text in the search field), and type to the console (F12 - Chrome, cmd+opt+C - Safari):
window.onmousewheel = function (evt) { console.log(evt.screenX, evt.screenY, 'wheel')}
window.onmousemove = function (evt) { console.log(evt.screenX, evt.screenY, 'move')}
Now, lets do some tests:
- move mouse, stop, then use wheel to scroll the page.
- Check console output (Safari):
[Log] 1916 – 558 – "move"
[Log] 1916 – 558 – "wheel"
-
Use your shortcut to zoom whole screen (cmd+opt+8, cmd+opt+"+" plus-btn )
-
move mouse, stop, then use wheel to scroll the page.
-
Check console output (Safari):
[Log] 1624 – 1255 – "move"
[Log] 2054 – 1279 – "wheel"
So, you see it uses incorrect mouse position for wheel events.
Note: In both cases we DON'T MOVE mouse for wheel events! (zoomed and non-zoomed tests above)
Explanation: "move" suffix - coordinates for mouse move events "move" suffix - coordinates for mouse wheel events
PS. It can be reproduced on Catalina v 10.15, Big Sur, and Monterey for any app, but you can play with the code above in Safari and Chrome. Hardware: iMac 2019.
Is it just me or is it the same for others? Is it possible to somehow fix this on my side or should We wait for a fix in new OS versions?