Ok, solved the thing but keeping the post just for help.
Turns out Autolayout frames have “memory”.
I added a stepped guide with a purple rectangle that would behave correctly when dropped into an autolayout frame, but when following the steps it gets as bad as red rectangle.
In short: When you set an object inside an autolayout frame to be “fill / fill” and then you drag it out of that object, it can no longer be “Fill/Fill” so it is set to “Fixed/Fixed”.
At this point Figma should reset this frame status and forget his “Fill/Fill” past.
But no, Figma is not going to do that. It will remember, it will never forget.
Guys, we need to learn to let things go…
After that, when you are thinking nothing is wrong, you drop the “Fixed/Fixed” rectangle into a new Autolayout Frame, and just like my EX Karen did, it brings back that “Fill / Fill” past that no one was asking for, and messes everything up.
Please Figma fix this bug, and while you are at it, all our broken relationships 🙂
You should report this as a bug. Even if the behavior is consistent, it’s gonna feel inconsistent for the user since it’s not communicated well enough.
Figma Help Center
Not coummunicated well enough?
The fact that the frame has “memory” is not communicated to the user, causing confusion.
Oh, i see!
I did already report the thing as a bug,
I vote for this. Fill instead of Hug default behaviour is mostly annoying when working with text inside Auto Layout. I understand that CSS block elements like div has a default behaviour to occupy the remaining vertical space (fill) but when designing in Figma that should be the other way around. This affects mostly text elements inside the Auto Layout container. Please fix this cause Text is not a block element
