-
-
Notifications
You must be signed in to change notification settings - Fork 59
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
Animation runs repeatedly in interactive mode with loop={false} #71
Comments
Relatedly, if one tries to circumvent this by taking a small section as your "play" section and then setting it as a "stop" section after the user leaves the section, it still doesn't work. If the user scrolls through the slice too quickly, it just jumps to the last frame: interactivity={{
mode: "scroll",
actions: [
{ visibility: [0, 0.3], type: "stop", frames: [0] },
{ visibility: [0.3, 0.31], type: "play", frames: [0, 38] },
{ visibility: [0.31, 1.0], type: "stop", frames: [38] }
]
}} |
Hey @zackdotcomputer Did you find a solution for this at the end ? |
No, sadly. |
I'm dealing with something similar right now.
The animation plays when in viewport, but every time I scroll a lil' bit while in view it starts playing all over again. https://docs.lottiefiles.com/lottie-interactivity/animation-modes#animate-when-visible-and-play-once This doesn't work with lottie-react unfortunately. |
Yes, I have same problem. You might add some loop of the animation end, and the problem will be solved
|
Describe the bug
When set to not loop and play the animation once in a block, the expectation I have is that upon entering the block the animation will play once and then not repeat. Instead, the result is that the animation plays once and then replays again on each incremental interaction.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The expectation would be that the playthrough would happen once while the user was in section 30%-100% and then not play again.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: