-
Notifications
You must be signed in to change notification settings - Fork 604
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
Disable pausing autoPlay on hover #55
Comments
Pausing autoPlay on hover is a good pattern as it puts some level of control back to the user looking at the gallery. IMO, removing it would be an anti-pattern. But I'm interested to hear what others think. If you would like to see this feature added to Flickity, +1 or subscribe to this issue. |
+1 A typical pattern for this could be if Flickity was used as a "full-page" background-slider for photography websites that you'd want to auto-cycle through. Not my personal preference, but a valid use-case nonetheless. |
+1 |
2 similar comments
+1 |
+1 |
+1 |
4 similar comments
+1 |
+1 |
+1 |
+1 |
+1! |
+1 |
3 similar comments
+1 |
+1 |
+1 |
+1 only if it's an option and not default |
+1 |
4 similar comments
+1 |
+1 |
+1 |
+1 |
+1 |
2 similar comments
+1 |
+1 |
I agree, that it's an anti-pattern, although judging by the number of +1 it seems a lot of people want it. |
+1 |
1 similar comment
+1 |
+1 Yes, it's an anti-pattern if the slider is part of the UI. I have a site, though, that uses the slider as a fullscreen background behind the content. I need to be able to disable the "pause on hover". It would be really nice to have the option, even though it would rarely get used. |
I agree that this is an anti pattern usually but when using flickity for full screen sliders this is an issue. +1 👍 |
+1 for full screen sliders it would be really helpful. |
Next version will have |
@desandro I had a quick question. I have custom left/right nav set up which is 50% split over the image, so if you hover over the left and click, the slider proceeds previous and if you hover over the right the slider proceeds next. By having this, however, it seems to have voided the hover and pause function as there is a higher z-index container over the slider. Is there any way to call the pause method so I could bind it if the user hovers over the higher z-index container rather than the slider? |
@richgcook Yes see metafizzy/flickity-docs#5 (comment) for the Player API |
Flickity v1.1.2 has been released with Thanks for all the feedback on this issue. 🌈 🐻 |
@desandro Amazing! Thanks! |
@desandro Ah right yes so I'd still need to use the Player API if I have custom left/right nav on a higher z-index over the slider. Be nice if you could add a selector to the |
Please ,when slide is clicked autoplay stops,i dont want that,how to make autoplay to work after clicking |
Fix double playPlayer * tag 'v1.2.1': 👷 build v1.2.1 🐞 Prevent double autoPlay starting 👷 build v1.2.0 📝 switch to npmcdn 🐱 Add .github with issue template 🐞 remove touchVerticalScroll logic, not needed 🐞 cellAlign w/ freeScroll on cellChange Add aria-label to previous and next buttons 🛠 add playPlayer, pausePlayer, unpausePlayer methods v1.1.2 in dist file banner comments build v1.1.2 Fix initializing with high initialIndex; hack to fix scroll jump after focus; Fixes metafizzy#76 add pauseAutoPlayOnHover option; Ref metafizzy#55 alphabetize bower.json dependencies
@dalvujovic I solved this by adding |
@dicktornfeldt that only works as long as you don't need to have anything clickable in the slideshow. In my case I have links that stop working with this approach. Here is one that keeps the elements clickable:
|
As far as I can tell, it's not possible to disable this as yet.
Is this in the works? If it not, can it be added?
The text was updated successfully, but these errors were encountered: