[BUG]: dotLottie player makes icon disappear after animation is played in comparison with lottie player

[mstakh]

Environment:

• node 16.10.0

• npm 7.24.0

• Angular 13.3.12

• Browser and Browser Version: Google Chrome Version 115.0.5790.170 (Official Build) (arm64)

What did you do? Please explain the steps you took before you encountered the problem.

Two players behave differently. In case of dotLottie player animation is played once (no loop, only autoplay) and than image disappears. In case of lottie player (same configs, no loop, only autoplay), animation is played and final frame remains.

• dotLottie player code: <dotlottie-player style="width: 48px" src="https://lottie.host/70af7a13-8a36-4c3a-be17-c6a98de21375/9TdibOoOsg.lottie" background="transparent" speed="1" autoplay></dotlottie-player>

• Lottie player code: <lottie-player style="width: 48px" src="https://lottie.host/15cc9e3f-d67e-4770-abb5-4fc9b5d118ef/JA1SfGCJrx.json" background="transparent" speed="1" autoplay></lottie-player>

What did you expect to happen? On both players, when animation is finished and no loop specified, remain last frame

What actually happened? Please include as much relevant detail as possible. dotLottie player plays the animation and hides/removes last frame in case no loop specified

Please provide a download link to the After Effects file that demonstrates the problem.

[bodymovin]

hi, can you report this issue on the lottieFiles repository? it seems that lottie-web is working correctly

[yikZero]

I encountered the same issue. I was initially using lottie-react along with a .json format, but I switched to the dotlottie format because it's tinier. Consequently, I switched to the @dotlottie/react-player.

When I was using lottie-react and .json, everything worked perfectly. However, upon switching to dotlottie and @dotlottie/react-player, disappearances occur when I hover to the last frame, and the graphic reappears and rewinds when moving away. All the code remained consistent throughout.

Solution

Upon troubleshooting, I found that the final frame in my AE file was blank, which turned out to be the cause. I am unsure of why the two players behave differently in processing the last frame. Nonetheless, as long as the final frame in AE is not blank, this issue should not arise.

@mstakh @bodymovin