Skip to main content

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


Show first post

92 replies

Thomas_Tom-B
  • New Member
  • 2 replies
  • October 7, 2024

Same here, we shared our struggle as Design System team to Figma France.
We try to align Dev & Design, this is very… annoying.
Happens all the time on every component. So we create “fake boolean property” on the upper container.

It complexifies the property panel / API and requests designers to do stuff manually.

Hope it will come soon 🙂


Autumn_Dawe-Baillie

Just +1 ing this to keep it relevant and boost the request. The way this is working today doesn’t align with how it works in code and is causing confusion for our developers and designers.


Roman67
  • New Participant
  • 12 replies
  • October 22, 2024

This bug breaks my expectation of how Auto layout set to “Hug” should behave, and it forces me to implement a workaround when creating flexible components that can toggle layers on and off.


Bethany_Beech1

This is making design of layout components with collapsible sections 100x harder than it should be. Instead of simply hiding a top section and having it collapse/disappear completely, I now have to add complicated workarounds to get the layout to behave as it logically should-- not holding any space or padding if no layer in it is visible. Please fix this.


Yvette_O
  • New Member
  • 6 replies
  • November 18, 2024

Does anyone have a hack/fix for this issue when using a negative gap for the items in the container that won’t collapse? The 0px fix doesn’t work.


Olha4
  • 1 reply
  • December 6, 2024

+1 ran into the same issue


Klindt_Fabian

In my opinion this feature limitation is a direct contradiction to what Auto Layout is supposed to do? Why would you intentionally add a feature limitation that makes the handover to developers so unneccessarily complicated?

In the Figma Learn article on Auto Layout it says: “Use auto layout to create responsive designs that grow to fill, shrink to fit, and reflow contents” and “Build lists that adapt as items are added, removed, or hidden” but it does not do that due to your feature limitation.

This issue is costing me and my team precious time not only during design, but also when collaborating with developers.


Klindt_Fabian

To everyone else following this topic: our workaround is creating sub-components. Let’s say you are building a card with an optional header, and this header is an Auto Layout containing a couple of different things (like an avatar and a time/date slot, for example, that are shown next to each other). Building the header as a separate sub component allows you to toggle it on/off in the card component. Exposing the sub component in the card component then gives you all the options you need (in this example, hiding either the avatar or the time/date slot independently from each other).

This is not ideal as you, theoretically, can turn on the header boolean and then turn off the two header booleans, which will replicate the bug that is being discussed here - but it does allow you to turn off the entire header.


Jiyeon_Yoo
  • New Member
  • 1 reply
  • January 15, 2025

+1 please fix 


Lea.P
  • New Participant
  • 14 replies
  • January 21, 2025

*Push +1
The workaround with subcomponents is not practicable.

This is absolutely not a feature. This is a bug.
And a biiiiiig problem for our design system.

It is not logical at all that auto layout frames keep their dimensions but all child layers are hidden.

Please fix this! thx


Tim_Print1
  • New Member
  • 2 replies
  • February 5, 2025

Really need a fix for this bug, it is completely illogical and breaks even fairly simple components with boolean contents.


Mads_Emmertsen2

+1 Hoping this gets fixed in the near future


  • New Member
  • 1 reply
  • February 20, 2025

+1 really need this to be fixed for design systems that our team implement


Andrei Gadoiu

+1. Though I understand the fear others have when dealing with a 0px height layer, this clearly breaks the way auto-layout works.


Alexander Girod

I guess AI is more important now than fixing this issue and provide real quality of life for professional users.


Fraser Hood

+1 this is starting and will continue to cause issues for designers and developers across our product teams


Kateryna13
  • New Member
  • 1 reply
  • March 27, 2025

+1 can’t properly use boolean show/hide in complex components


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