@bentrengrove Hello. We are affected by this problem pretty seriously because we use a lot of animated webp images in our app. Coil is using DrawablePaint for Drawables.
I wonder is there a chance this can be merged and release soon so we can ask coil to do an update?

We now use a custom version of AsyncImage and in it we use a modified DrawablePainter, but people can easily forget about the problem and use the vanilla AsyncImage which still have the problem.

Thanks in advance.

Unfortunately, this is intentional behaviour. I suggest forking this implementation if that is what is required for your use case, we couldn't ship this because we would suddenly be scaling every drawable.

This was previously closed here https://github.com/google/accompanist/pull/1771/files

@bentrengrove How about adding condition to apply this only for AnimatedImageDrawable on systems below Android 12? This is definitely wrong rendering behavior and not intentional. The root cause is in the framework base, but that's not something we can change now.

Otherwise, I can only suggest coil to make a fork and fix this, and I don't think the position off is intentional, although it's AnimatedImageDrawable who was not following the spec.

OK. Yes, I would accept a PR that only applied this workaround as you describe. On Android <12 and for AnimatedImageDrawable. Would you be willing to make those changes?

No problem. I will make that change today. Thank you very much for considering this!!!

I've made the changes. Let me know if anything should be further adjusted. Thanks

Looks like you just have spotless errors

./gradlew :drawablepainter:spotlessApply

Okay. It's done.

This has been released as 0.37.3

thank you!! ❤️