-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
User can Scroll in Windows leading to bad render #438
Comments
Thanks for a detailed report. Is it happening for you also in the example presentation (home page of impress.js)? |
I forked this impress and updated code to add scroll event handler to go to next slide. https://github.com/radicaldrew/impress.js/blob/master/js/impress.js#L681 document.addEventListener("scroll", function ( event ) { |
Apologies if this is the wrong place to ask. I was wondering if there is an ability (planned maybe) to support zoom in/zoom out behaviour for mousewheel/touchpad so that panning and zooming is possible independently from the steps order. Couldn't find a plugin that does this, but maybe I'm not looking in the right places. Thanks for any help! |
The right place to ask would be to just file a new issue |
Thnx @henrikingo I've done so. Would be happy to help with implementation, but I'm not up to speed with the code base yet at all. |
I just tested with Microsoft Edge and this seems to no longer be happening. Can you confirm? |
It's fixed. We can close this issue, although I think that I might want to implement such a zoom plugin |
The middle mouse button scroll in Windows causes glitches in render. I have attached screenshots below from one of my presentations.
Moreover, I can scroll indefinitely in either axes using the same middle mouse scroll when the rotate transforms are used (only in Firefox).
Wheel scroll also causes slides to rearrange on the display.
This issue is not reproduced in Linux using Firefox.
Normal view (Chrome 38 on Windows):

After scrolling using wheel (Chrome 38 on Windows):

Firefox keeps the backgrounds intact, though.
The text was updated successfully, but these errors were encountered: