New Member

Solved

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

Forum|Forum|5 months ago
April 9, 2026
36 replies
573 views

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.

Best answer by Celyn_L

Hi everyone, thanks so much for your patience here. We’ve now rolled out a fix, and this issue should be resolved.

Could you please try the following steps:

Reload your tab or client
For any affected slots, either regenerate the instances using the tool or click into them to refresh

They should now update correctly after this and continue to behave as expected on subsequent refreshes without needing repeated manual interaction.

If you’re still seeing the issue after trying this, feel free to share a quick screen recording and we can take a closer look 🙌

Ben_Smeets

Active Member

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.

Casey3Author

New Member

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

Ben_Smeets

Active Member

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

Ben_Smeets

Active Member

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

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

Ben_Smeets

Active Member

It is also related with components that have slots-with-components-that-have-slots….

Feels like a total bug.

Celyn_L

Figmate

Hi @Casey3 @Ben_Smeets, Celyn from Figma Community Support here.

Thanks both for sharing such detailed context — especially around how this is showing up with shared libraries and Slot-based components. The notes around cross-user differences and the layout correcting on interaction are really helpful.

From what you’ve described, it sounds like layers set to Fill container aren’t rendering correctly on file load, and only snap into place after interacting with the frame.

I’d like to take a closer look at this with the team. To help us narrow this down, could you share a couple quick details:

If you insert the same component into a brand new file, does the issue still occur?
If you detach one of the affected instances, does the Fill container behavior still require interaction to render correctly?

It would also really help if you could:

Share a link to an affected file
Invite support-share@figma.com with Can view access (this will not impact your billing and will allow us to reproduce the issue and investigate with Engineering)
Share a screen recording showing the issue in action (if possible) — @Casey3, looks like the recording didn’t come through in your original post, would you mind re-uploading it?

I’ll also raise this with the team based on what’s been shared here. Really appreciate you both flagging this — I’ll follow up here with any updates.

Ben_Smeets

Active Member

I’ll try and make some time. It would be the easiest if someone jumps on a call with us. Helps us feel Figma is invested in fixing it as well :) But I’ll try to fix a screen recording.

P.S. I’m not discussing this with an AI bot am I (em-dash walhalla and all)?

Celyn_L

Figmate

Hey @Ben_Smeets, thanks for your reply.

I hear you. While we can’t jump on a call, just wanted to reassure you that the team is already looking into this closely.

No worries at all if you’re not able to put together a screen recording. If it’s easier, sharing a link to the affected file with “Can view” access would already be super helpful for us to take a closer look.

Really appreciate you working through this with us, and thanks for your patience in the meantime.

PS: You’re definitely talking to a real person here from the Figma Community Support team 🙌

Ben_Smeets

Active Member

PS: You’re definitely talking to a real person here from the Figma Community Support team 🙌

That’s what an AI would say (jk)! 😁 Cheers, Ben

Show more replies

Sign up

Login with SSO

Login to the community

Login with SSO