-
Notifications
You must be signed in to change notification settings - Fork 23
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
Maybe touch-action:none; only after first Zoom Event ? #36
Comments
This is indeed a tricky situation, because set On current situation, maybe you can try these following code:
I will try to find a solution to this problem and maybe fix it in the next version. |
Hey @VonZubinski , Thanks for your suggestion, I implemented it on Sorry for taking so long time, enjoy it! |
@cotton123236 Thanks, this mostly works. However I noticed that on mobile, the first scroll gesture does nothing. Only after removing the scrolling finger form the screen, and scrolling again, the scrolling actually works. So there seems to still be a small bug there. |
@jaco-terbraak |
@cotton123236 Fair enough, thanks for looking into it |
I would really like to use Zoomist in a current project, unfortunately, if implement on mobile the whole image container becomes a "deadzone" for scrolling. Especially when a bigger portrait image occupies a lot of screen real estate, the user has to search for some left over whitespace to continue scrolling.
To counter this problem, I was planning to set the container class to
touch-action: manipulation;
and change it tonone
in case of a zoom event.From my understanding, I would have to give every container some kind of id-name and have it initialised separately.
Is it possible, to keep that naming global and trigger that css change with
zoom(zoomist, scale) {...}
only for the zoomist-container that is being used ?The text was updated successfully, but these errors were encountered: