Skip to content
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

Autoplay transitions funky in Safari #1

Open
zmre opened this issue Nov 3, 2023 · 4 comments · May be fixed by #3
Open

Autoplay transitions funky in Safari #1

zmre opened this issue Nov 3, 2023 · 4 comments · May be fixed by #3

Comments

@zmre
Copy link

zmre commented Nov 3, 2023

Just discovered your project and it looks great. In testing it out though, I noticed the autoplay functionality looks pretty funky in Safari on MacOS. It seems to go back to the beginning and then slide to the next slide and then stutter for a minute. I made a short gif to show what I mean:

2023-11-03 17 19 30

I suspect it is something to do with the scroll animation routine. Not sure if CSS transition stuff and a element.scroll({...behavior:"smooth"}) would be a simple workaround. I've only just taken a peek and made a guess. Hope the bug report is welcome.

@zmre
Copy link
Author

zmre commented Nov 3, 2023

I should note: every other way of triggering a change works great -- clicking arrows, scrolling, dragging, etc. It's only the autoplay that's funky as far as I've noticed.

@zmre
Copy link
Author

zmre commented Nov 10, 2023

This is not going to work in production for us. Really hoping you have a chance to look at it so we don't have to change directions at the last minute...

@bugproof
Copy link

bugproof commented Sep 30, 2024

@zmre it seems like autoplay uses scrollTo instead of navigate function so maybe it's just a matter of changing that. This is still probably one of the best open-source carousels you can find with that kind of performance. What carousel have you settled on?

@bugproof
Copy link

bugproof commented Oct 23, 2024

@zmre it's fixed. It's up to @beynar now to merge #3 and release it

@bugproof bugproof linked a pull request Oct 23, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants