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
Touchmove (iOS) stops animation loop #21
Comments
The swiping animation is working as intended. Pausing the animation loop is exactly what should happen when pauseOnAction is true, because a swipe is a declared action by the user. pauseOnHover is not a usability concept that applies to mobile, so if you don't respect pauseOnAction, sliders will get out of control and have seemingly random movements on the user. Your issue sounds like a personal usability preference, which is fine. You can totally accomodate this. Use the after() callback to call slider.resume(). This will resume the slideshow after the animation has completed. |
Yes, animation is working as intended. But I set pauseOnAction on 'false' — and I think the animation loop should then restart/resume after swiping is done. Meanwhile we tried the after-callback-solution, but then, after the first completed animation loop, flexslider is getting wild! It slides in very short intervals — uncontrollable. |
Update: Got it working with a little workaround: animation: "slide", //String: Select your animation type, "fade" or "slide" We had to first .pause() before .resume()! Otherwise flexslider goes crazy: after: function(slider){ slider.pause(); slider.resume(); }, |
@rocketjoe put this up on a gist. Its pretty useful. |
On Flexslider 2 resume doesn't work. after: function(slider){ slider.pause(); slider.play(); }, and then is OK. Tested on my mobile and working. |
@briandowmobile what version within the 2.x.x release versions do you mean? |
After sliding on iOS (touchmove), the animation loop stops regardless pauseOnAction or animationLoop settings. After sliding left or right the animation should resume.
The text was updated successfully, but these errors were encountered: