Lottie matte rendering artifacts with lines about dotlottie-web

[theashraf]

@andrewvarga Hello, we checked this, and it is not a dotLottie issue but a lottie-web problem (https://github.com/LottieFiles/lottie-player). So, you shouldn't have any problems with dotLottie-web. Thanks.

Thank you! I think we should we switch to this dotlottie player from lottie-web, it seems it's more mature - do you agree? Do you foresee any possible downsides for this? The way I see dotlottie player also supports simple "json" lottie files, besides the binary dotlottie format so that shouldn't be an issue.

One significant advantage of the dotLottie player over lottie-web and lottie-android is its consistent rendering. This consistency is achieved by using the same rendering engine (ThorVG) across all dotLottie players, with a single core codebase (dotlottie-rs) that is cross-compiled to Kotlin, Swift, and WASM for web use. While describing it as more mature can be subjective and depends on the specific Lottie animation features in use, the dotLottie player does support some features that lottie-android does not, and vice versa.

In my opinion, the primary benefit is the ability to play .lottie format files, which are smaller in size compared to the standard lottie json format.

[hermet]

@andrewvarga Hello, we checked this, and it is not a dotLottie issue but a lottie-web problem (https://github.com/LottieFiles/lottie-player). So, you shouldn't have any problems with dotLottie-web. Thanks.

[andrewvarga]

@andrewvarga Hello, we checked this, and it is not a dotLottie issue but a lottie-web problem (https://github.com/LottieFiles/lottie-player). So, you shouldn't have any problems with dotLottie-web. Thanks.

Thank you! I think we should we switch to this dotlottie player from lottie-web, it seems it's more mature - do you agree?
Do you foresee any possible downsides for this? The way I see dotlottie player also supports simple "json" lottie files, besides the binary dotlottie format so that shouldn't be an issue.