Skip to main content
Question

Flickering auto-layout size of an element

  • April 2, 2026
  • 4 replies
  • 35 views
Adama

Hi.
I noticed a bug on figma auto-layout element.
Structure : A form ui with a auto-layout frame (size: 520px), with two elements (inputs) inside. One input component (the main component) and another instance of that component (220px for each element, fixed sizes).

When i select the main component and set it’s width to fill container (instead of fixed), the sizes keep “flickering” (growing and shrinking infinitely).

I think it’s due to the other instance inheriting the fill container, while the other one is resizing..

4 replies

Alex_12l3kj29

Can confirm! Here’s a loom for context:
 https://www.loom.com/share/5d1ad7abc39746c4b90dc08a944e3012

Jaycee Lewis
Figmate

Hey, ​@Alex_12l3kj29  👋 Thank you for the Loom. Thank you ​@Adama for the initial report 🙌

To narrow this down, a few details would help:

  • Is the 520px frame set to Hug or Fixed on its width?
  • Are you on the desktop app or browser, and which version?
  • Does it still flicker in a brand-new auto layout frame set to Hug width, with one child set to Fill?

In the meantime, if the frame is on Hug, try setting it to Fixed first, then set the input to Fill — that can help with this kind of flicker.

That'll help us tell whether this is a sizing conflict or something else to look at. Talk soon! — Jaycee

Alex_12l3kj29

​@Jaycee Lewis

 

The frame width in my case is set to Fixed. This occurs only when putting text components into an auto-layout. For every other component (frame / auto-layout) the container has w:hug initially and behaves correctly when only setting one child to w:fill.

My example however also behaves correctly when setting all children to w:fill. The problem seems to be that the second child, although it’s a component instance, won’t get w:fill but keeps w:hug

 

I’m on Figma Desktop App version 126.3.12 (macOS Apple Silicon)

Jaycee Lewis
Figmate

Hey, ​@Alex_12l3kj29  ​@Adama 👋 I couldn’t repro. Would you be able to provide the following in a support ticket?

  • Share the URL of the affected file(s)
  • Grant edit access to support-share@figma.com so our team can attempt to reproduce the issue
  • Include a full-size screen recording of the issue, if possible (your Loom is great)
  • The OS, Desktop or browser, versions 

Sharing file access won't impact your billing — it just allows our team to debug further on their end. Please be sure to use your Figma email account when sharing.

If so, we can get you to support. — Jaycee

Terms & ConditionsAccessibility statement