Thanks for the +1
I changed the topic to a feature request to add weight to our complaints! Vote away
+1. I expected that wrapper of hidden booleans also would be hidden.
I’m glad, that you opened this topic.
Same here, would expect it to work the same way as CSS. Very difficult to create scalable and reasonable components.
Hi Figma team, is this topic part of a possible update?
+1. Please fix. The current implementation is not very intuitive imo.
Just to bump, as it’s still not fixed. We need this.
Ran into the same issue, still not fixed.
FigJam has AI features now, but we struggle with containers that don’t resize if they are empty 🤣
Still experiencing this issue on our components and unable to use a 0px object either.
Can confirm this is a problem we’re encountering with multiple components in our design system, seems obvious that a frame with dimensions set to “hug” should shrink whenever any of its contents are hidden, including the last child, and when all of its contents are hidden it should shrink to zero in the hug dimension(s). Please make it so.
+1. Cant find any workaround, should be possible to collapse to zero
+1 Thanks for reporting this! Seems like an obvious bug.
+1 to all the above comments. I would even tend to add that the auto-layout frame having all child hidden should also be hidden. Reason being if this frame is within another auto-layout frame with spacing between them, the spacing would remain even though one is empty with a 0px height.
There would probably have tweak around even without this addition, but it would probably make our life easier.
Same here, having the same issue and need… Thanks for looking into it Figma!
+1, this is making me so sad 😦
+1. Currently using the 0px Frame hack as a workaround.
This is a very frustrating bug and should be fixed. It affects the usage of boolean properties.
Ran into this error today as well… It was not that big of a deal, since i just built a separate component for my case, but still when you are in the hour before the deadline of your final Bootcamp presentation, these kind of bugs aren’t something you want to figure out in this kind of situation… 🤭
Bot sure if it’s a bug. I often use empty AL containers similar as one would use an empty div container: A placeholder for things that might appear in that section but are currently not visible.
bump so that this topic will not auto-close.
+1. This bug forces me create another frame with another boolean prop to hide the empty frame.
+1. This is super frustrating. A container set to size to its contents that has no contents should be zero.
I have a stack of components that I need its autolayout parent container to hug vertically, and it can’t because its children are taking up phantom space. Makes no sense.
I cannot believe this is the condition of this feature.
Just encountered this too. This should behave the same as CSS whereby display: none child elements don’t affect the height of the parent, so the parent collapses in height if all children are not displayed
Just adding another +1 to keep this issue open
If the frame height is set to “Hug” it shouldn’t have a height when it’s empty or when the elements inside it are hidden.
This is the challenge with Figma lately, all the focus goes to random new “features” but less attention to stuff that (even after years) is still not working 100%… sigh.
