Skip to main content
Question

[Bug] Fill Container Width Not Rendering Until Frame Is Clicked (Shared Library Components)

  • April 9, 2026
  • 5 replies
  • 22 views

Casey3

Hey everyone,

I've been dealing with a frustrating bug lately and wanted to post here to see if anyone else is experiencing the same thing — and to get it on Figma's radar if it hasn't been reported yet.

---

**The Bug**

Components from my shared library that are set to **Fill container** (horizontal) are not rendering correctly when a file is opened. They appear collapsed or incorrectly sized — but the Fill property is still correctly set. The moment I click anywhere on the affected frame, it instantly snaps into its correct filled state. No property changes, no workarounds — just a click.

I've attached a short screen recording that shows this clearly: a **Save and Cancel button pair** is initially invisible inside their container, and after I click the frame they snap into the correct position immediately.

---

**Why It's a Big Deal for My Workflow**

This is causing real problems for our design-to-dev handoff. Our developers use Figma specs as the source of truth for building components. When frames aren't rendering their Fill correctly, devs see broken layouts and build accordingly — and since they're on a plan that doesn't allow editing design properties, **only I can fix it.** That means I have to manually go through files, click frame by frame to trigger the correct render state, and verify everything before every handoff. It's not scalable.

---

**Details**
- Figma Desktop App (latest version)
- Shared component library used across multiple project files
- No consistent trigger — happens randomly, possibly related to slot-based components

---

Has anyone else run into this? Any known workarounds while this gets resolved? Would love to know if this is isolated or a wider issue.

5 replies

Ben_Smeets
  • Active Member
  • April 10, 2026

I have the exact same issue. Have to start each day by double clicking all frames (dozens) to make sure the layout is snapped correctly.
 

It looks like it might be related to Slots. Is that on your end as well? Meaning, stuff that is sized incorrectly is what is in a slot.


Casey3
  • Author
  • New Member
  • April 10, 2026

From what I have observed thus far, yes it appears to be related to my global library components with slots.


Ben_Smeets
  • Active Member
  • April 13, 2026

Anyone from @figma that can have look/give a reply?


Ben_Smeets
  • Active Member
  • April 13, 2026

Additional info:

  • User A → Everything ok
  • User B → Shows wrong rendered slot content
     
  • User B double clicks the item → Rendering fixed
  • User A/B → Closes figma and opens again → Everything wrong again

Ben_Smeets
  • Active Member
  • April 13, 2026

It seems related to the multiplayer options, like it is not updated across instances of Figma. Only if you click it.