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
iOS #4
Comments
Arron - I haven't explored it much with iOS. I don't have an iPad or iPhone and On Wed, Jun 13, 2012 at 10:17 AM, Arron Mabrey <
Follow me on Twitter: http://twitter.com/johnpolacek |
John, -- Arron On Wed, Jun 20, 2012 at 9:37 PM, John Polacek <
|
@arronmabrey Wanted to see if you ever pursued this? I need to accomplish something similar. |
I've been toying with the idea of creating a scrolling plugin that toggles a css animation triggered of scroll points. I'd probably build it on top of jquery transit. http://ricostacruz.com/jquery.transit/ SuperScrollorama can do some pretty crazy things, but for smaller scale stuff like a lot of people do, and to get it to work well on mobile, something like that would make more sense. |
I would love it if you could get it to to work on iOS. just saying. |
Hi! The plugin was just updated to help you get it working on iOS. |
I noticed the animations don't playback when scrolling on iOS, I know its because safari doesn't execute JS when scrolling to keep the user interaction performant.
My question is could superscrollorama be integrated with something like jScrollpane (http://jscrollpane.kelvinluck.com/) where superscrollorama would listen to jScrollpane events vs the native window scroll events?
Besides changing which scroll events to listen to are there any other considerations I may be missing?
Is there an issue with my "target elements" or "pages" being wrapped inside the jScrollpane DOM elements and not directly inside the body tag? Would it throw off any offset calculations or anything of that nature?
Have you tried anything like this before, if so, for what reason did you abandon it?
Thank you John for your contributions.
The text was updated successfully, but these errors were encountered: