Consider attaching `className` to the outer-most container about lottie-react HOT 5 OPEN

hi @kdembler

Have you tried overriding .lf-player-container with your own CSS?

It doesn't have any styling on our end, and was left for user's to add their own.

from lottie-react.

Yes, we tried that. The issue is that like I said we would like to avoid having styles based on the .lf-player-container class in our codebase as we may want to switch to a different lottie library in the future without things breaking (we just switched to this one :)). So like I said, ideally, the internal implementation of the library (container class name) wouldn't need to leak inside our codebase

from lottie-react.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs.

from lottie-react.

Would it be possible to recheck this?

One of the solution is to replace <div className="lf-player-container"> with React Fragment <> so it doesn't create div without any styles and usages.
It's pretty simple to add existing container by yourself.

Another approach would be adding props for styling lf-player-container as @kdembler mentioned

from lottie-react.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs.

from lottie-react.