+1 I can’t believe this is still an issue
Figma please fix this. Having to add an extra frame is a dumb workaround and is confusing when I handoff my file to dev and have to explain it.
Hey All, thanks for the feedback and so sorry for the delay!
Our team is proactively working on this and hope to have a fix soon - stay tuned!
I can’t wait until this is fixed! I have been running into this issue for some time, and I need it to collapse to zero for both height and width! Thanks!
@Jared_r Totally agreed. Still waiting for this…
Hey All, sorry for the delay!
The solution our team put together was more complicated than they originally anticipated, so the team had to gather more heads to collaborate to get this working as expected.
We’ll be sure to provide an update as soon as we can, but also keep an eye out on our future releases.
I’m running into this today. I have a list of fixed size where items only appear if they are selected on a parallel list. If I select the, say, third item in the list, it appears fine… except two rows down. It makes no sense for it to be doing this when the width & height of the still-hidden items is set to 0.
Glad to hear a fix is on the way.
Keeping this alive until it is resolved…
Puh-lease, please fix this. We’re two years in now … 🥴
Run into this today, definitely need solution for this
Annoying, but at least it’s easy to work around with a transparent 1px width/height frame in the autolayout.
Please fix this. It’s making the use of auto-layout and boolean props impossible to use with complex components.
Still struggling with the same issue of auto layout not fully collapsing when all of the layers within it have been hidden. Eager to see what solution is ultimately created by the Figma team 👀.
+1. I am struggling with this issue.
+1 also struggling with this still.
If you use the Line tool and draw a line with a transparent stroke (do not draw a 1px rectangle as a line), then it should collapse to 0px since lines drawn with the Line tool don’t occupy layout space.
just dropping in to say this issue still persists… After 1 year with many people having that issue 😢
(0 width object hack luckily is still working tho… (0 width item has to be set to visible with 0 opacity to work & look properly))
Hi all, seems like the bug is not fixed yet, so I too am keeping it alive.
So anyways if anyone need some help, @Tascha 's 0 pixel 0 opacity object is the only workaround
Your idea worked and helped me a lot, thank you!! 🙏 @Klesus
I’m having this issue even with AL frames with padding and/or min height set, both of which would intuitively prevent frames from collapsing to 0 height/width! I should fully be able to make an empty AL frame with padding that hugs its contents, but … I cannot.
Really annoying!
One of the hardest parts is that the UI doesn’t update – it still says “hug” for the height even though it’s “hugging” around a non-existent child element. At minimum the UI should update to make this more clear – switch it to “fixed” and prevent me from choosing “hug” unless there’s children. That would suck but at least it would be clear that something is happening.
Also encountering this as an issue. I have elements stacked vertically in an auto-layout. I’d like to have a boolean to show/hide an element but Figma doesn’t collapse the height of a component so the empty space still shows when the boolean is turned off. I’d expect it to collapse. Fixed height / hug should allow the designer to dictate whether it collapses or not.
Hey All, thanks for your continued feedback, and we apologize for the confusion caused by this!
As mentioned above, this is behavior is currently a known feature limitation in Figma.
We do not allow Auto layout frames to collapse to 0 when the child layers are hidden, so it is expected that the frame will remain sized as if they were shown.
Again, the team’s original solution was more complicated than they originally anticipated. They will need more bandwidth and more heads to collaborate to get this working as expected.
Our team is still actively tracking this as a feature request and quality improvement for future prioritization. Rest-assured that every new comment is being added to our our open report to give this topic more visibility so that it can be pushed to the top of the team’s priority list.
We’ll be sure to provide an update as soon as we can, but also keep an eye out on our future releases .
Thanks @dvaliao!
I just want to comment to keep focus this to the degree that I can because it’s just so important to get this release.
