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 🙌

Show previous replies

stevekulaga

New Member

I’m having the same issue as well, it’s a bummer.

Celyn_LAnswer

Figmate

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 🙌

D

Denise Chow

New Member

@Celyn_L I’m still having the same issue where components aren’t rendering correctly until I click into them since the fix a couple weeks ago

It will start out fine but then when it’s being reviewed in app or browser by someone else it seems to revert to this bizarre layout.

When I try to click into the components to update them in the app, it doesn’t seem to update the web app. So I’ll end up clicking into the components on web too just to fix it

It’s been happening in my templates and I can’t tell if its my file or a bug.

Usually I need to click into the main component to fix it visually across the board

I don’t have screen recordings at the moment, just screenshots

My app is completely updated and I’m not using slots

Celyn_L

Figmate

Hi @Denise Chow, thanks for following up here and for sharing the additional context.

I understand that you’re still seeing the component rendering issue even after the earlier fix, and that the layouts seem to correct themselves only after manually clicking back into the main components.

Would you mind sharing a link to one of the impacted files so we can take a closer look into the behaviour? Please also invite support-share@figma.com with “Can View” access so the team can investigate further (this won’t impact your billing).

Appreciate you taking the time to report this and help us dig into it further 🙏

D

Denise Chow

New Member

@Celyn_L just added support to the file

Celyn_L

Figmate

Thanks, @Denise Chow - when you have a moment, please share the file link with me here or via DM, and I’ll pass it along to the team for further investigation 🙏

Ben_Smeets

Active Member

We also have the same issue again (still). As soon as something is in a Slot, multiplayer is broken.

Ben_Smeets

Active Member

@Celyn_L Any updates on this? It seems to be exactly the same issue as before (no point in waiting for examples I think, it’s the same issue).

Celyn_L

Figmate

Hi @Ben_Smeets, thanks for following up - I'm sorry to hear you're running into this again.

I've shared this with the team so they're aware that users are still encountering this behavior.

I've gone ahead and created a support ticket for you so the team can take a closer look and investigate further. Your ticket number is #1938977.

When you have a moment, it would be really helpful if you could reply directly to the ticket with a link to the impacted file and invite support-share@figma.com with Can View access. This won't affect your billing and will allow us to reproduce the issue and work with Engineering on a deeper investigation.

Thanks again for taking the time to flag this. Someone from the team will be reaching out with next steps shortly.

Anne Müller

New Member

I have a similar or maybe even the same issue reported here:

Show more replies

Sign up

Login with SSO

Login to the community

Login with SSO