IssueTracker

Can you attach / share a project that reproduces the issue?

I'm sorry to say, but it's somewhat disheartening to take time to create a project for one bug, just to see it quickly being closed as "Won't fix (Intended behavior)".

Especially, as I was available to answer any questions and we ended up confirming that there was some sort of confusion about the intent of the project.

Sorry for the confusion and thanks for the project I did download and run it.

Maybe I am missing the issue. What do you think is the bug?

As I understand it:

• MotionLayout has ability to set setters
• ImageView does not have setPadding(float)
• You worked around it by writing a setPadding setter in a subclass All this is working as intended.

I thought your use of fun setPadding(size: Int) = super.setPadding(size, size, size, size) was a bit of a problem because padding is dimension

I will re-open it

I reported the issue, because I think that the ImageView is not properly applying the padding.

I'm only using MotionLayout, because I could consistently reproduce the problem with it. However, I believe that it has nothing to do with the problem.

I believe this an ImageView issue. I noticed that, even though ImageView outline is invalidated, it's frame is not properly updated and that results in a visual bug.

Please take a look at PaddingImageViewFixed, which tries to fix the issue, and does so by enforcing that setFrame is always called.

I don't fully remember the workflow, but, looking at the comment in PaddingImageViewFixed, it seems that ImageView.configureBounds() is related.

Thank you. 🙏

This was added to the "MotionLayout" issues and I was viewing it as such. I will assign to someone who might know more about ImageView

Thank you.