-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Zooming with a Magic Mouse or trackpad is too fast #15423
Comments
devices/os On some device and os the mouse zoom wheel was unusable (one scroll step would result to full zoom in or out). A user reported this per email and I had the issue on my private windows machine with its touchpad and with 2 different mouses. Strangely the same mouse were working fine with my HP Zbook on linux. See also openlayer issue openlayers/openlayers#15423
I had the similar issue using the |
Just one note from a user's perspective: I find OpenLayers apps with |
devices/os On some device and os the mouse zoom wheel was unusable (one scroll step would result to full zoom in or out). A user reported this per email and I had the issue on my private windows machine with its touchpad and with 2 different mouses. Strangely the same mouse were working fine with my HP Zbook on linux. See also openlayer issue openlayers/openlayers#15423
Describe the bug
Users and I are experiencing super fast zooming on our private maps when using a Magic Mouse or a trackpad.
It is quite unusable since in like 2, maximum 3, standard "wheel" moves the map jumps from street level to world view.
The zoom seems really too sensitive, while on other mainstream maps websites it's not the case.
To Reproduce
Steps to reproduce the behavior:
We are using OpenLayers v6, but as described, we have the same behavior with current examples from
main
branch.It seems that before our upgrade to v6, such behavior did not exist.
Our maps always has
constrainResolution: true
.Expected behavior
Zooming with a trackpad should be less sensitive.
WIP: I'll prepare a PR soon, as I analyzed and possibly found a condition that should be inverted to be more logical to me.
(related to #10672 changes)
The text was updated successfully, but these errors were encountered: