Skip to main content
Casey3
New Member
April 9, 2026
Solved

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

  • 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 🙌

36 replies

Ben_Smeets
Active Member
April 14, 2026

We have a file that can reproduce the issue. Invited support. Challenge with recording it, is that part of the issue seems to be that it’s in the multiplayer sync. So we can’t easily record both screens at the same time.

Ben_Smeets
Active Member
April 14, 2026

Managed! Here we go, will be a bit of a challenge to decipher it but it shows how user A does stuff, user B doesn’t see the changes until clicking on the item.

 

The challenge is the “not getting updated” part, but I think we followed the thread to this multiplayer issue (not sure).

 

https://drive.google.com/file/d/1P5v5zn_ckJ0SmLlMTON0zhsz70cqhluw/view?usp=drive_link

Celyn_L
Figmate
Figmate
April 15, 2026

Thanks so much for getting that recording together ​@Ben_Smeets. I can imagine that wasn’t easy to capture, especially with the multiplayer aspect, so really appreciate the effort here 🙏

I tried opening the Drive link, but it looks like I don’t have access at the moment. Would you be able to update the permissions to “Anyone with the link can view”?

Also, thanks for inviting support to the file - could you share the file link here as well?

Thanks again and appreciate you working through this with us!

Ben_Smeets
Active Member
April 15, 2026

Thanks so much for getting that recording together ​@Ben_Smeets. I can imagine that wasn’t easy to capture, especially with the multiplayer aspect, so really appreciate the effort here 🙏

I tried opening the Drive link, but it looks like I don’t have access at the moment. Would you be able to update the permissions to “Anyone with the link can view”?

Also, thanks for inviting support to the file - could you share the file link here as well?

Thanks again and appreciate you working through this with us!

Jup sure, done 👍

Celyn_L
Figmate
Figmate
April 17, 2026

Hey ​@Ben_Smeets ​@Casey3, thanks for sticking with me while I checked in with our engineers.

The team is aware of this issue and is in the process of rolling out a fix over the coming weeks.

I’ll share another update here once the fix has been fully rolled out.

Thanks again for your patience 🙏

Ben_Smeets
Active Member
April 17, 2026

Hey ​@Ben_Smeets ​@Casey3, thanks for sticking with me while I checked in with our engineers.

The team is aware of this issue and is in the process of rolling out a fix over the coming weeks.

I’ll share another update here once the fix has been fully rolled out.

Thanks again for your patience 🙏

Coming weeks sounds like a long time! Good luck :)

Ben_Smeets
Active Member
April 17, 2026

Can I just add… the last couple of weeks the amount of (very minor, but still...) bugs seems to have been increasing a bit. Hope this is not the new normal (stop vibe coding! 😉). My 2 cents.

Ben_Smeets
Active Member
April 22, 2026

Hey ​@Ben_Smeets ​@Casey3, thanks for sticking with me while I checked in with our engineers.

The team is aware of this issue and is in the process of rolling out a fix over the coming weeks.

I’ll share another update here once the fix has been fully rolled out.

Thanks again for your patience 🙏

Coming weeks sounds like a long time! Good luck :)

Saw an update incoming thought surely the bugs would have been given some priority… ChatGPT support improved! Must be important as well... 

Ben_Smeets
Active Member
May 1, 2026

Hi ​@Celyn_L , did you hear anything back regarding timeframes for the “fix”? Cheers and thanks, Ben

Celyn_L
Figmate
Figmate
May 4, 2026

Hey ​@Ben_Smeets - thanks for following up, and really appreciate your patience here.

From what I understand, the team is still actively working on a fix. I’ve just done a quick check-in with them as well, and I’ll follow up here as soon as I have any updates.

Thanks again for bearing with us in the meantime 🙏