Skip to main content

"Empty" Auto Layout Frame keeps the size of last hidden child


Show first post

92 replies

Antoine
  • Author
  • 144 replies
  • July 10, 2023

Thanks for the +1
I changed the topic to a feature request to add weight to our complaints! Vote away


verymoko
  • 4 replies
  • August 25, 2023

+1. I expected that wrapper of hidden booleans also would be hidden.

I’m glad, that you opened this topic.


Peter_Pilat

Same here, would expect it to work the same way as CSS. Very difficult to create scalable and reasonable components.


Frederic_Giroux

Hi Figma team, is this topic part of a possible update?


OliverM
  • 1 reply
  • September 26, 2023

+1. Please fix. The current implementation is not very intuitive imo.


Kharboush_Anton

Just to bump, as it’s still not fixed. We need this.


Helge_Wadewitz

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.


Celestine
  • New Member
  • 4 replies
  • November 16, 2023

+1. Cant find any workaround, should be possible to collapse to zero


alexrest
  • New Participant
  • 12 replies
  • November 21, 2023

+1 Thanks for reporting this! Seems like an obvious bug.


Frederic_Giroux

+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.


Nicolas_Combes

Same here, having the same issue and need… Thanks for looking into it Figma!


Scott_Daly

+1, this is making me so sad 😦


Peter_Laxalt

+1. Currently using the 0px Frame hack as a workaround.


Nelson_Vasconcelos2

This is a very frustrating bug and should be fixed. It affects the usage of boolean properties.


Philip16
  • 1 reply
  • December 23, 2023

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… 🤭


FlorianModel

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.


MichaelF
  • New Participant
  • 13 replies
  • February 6, 2024

bump so that this topic will not auto-close.


stevekulaga

+1. This bug forces me create another frame with another boolean prop to hide the empty frame.


Aaron5
  • 1 reply
  • February 15, 2024

+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.


Seamoose
  • 3 replies
  • February 15, 2024

I cannot believe this is the condition of this feature.


Andrew_Elliot

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


Dustin_Hansen1

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.


Ben_Smeets
  • New Participant
  • 38 replies
  • February 29, 2024

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.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings