Skip to main content
Casey3
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

    Show previous replies
    Gayani_S
    Figmate
    Gayani_S
    Community Support
    June 2, 2026

    Hey ​@Anne Müller, thanks for flagging this. I’ve followed up on your original post. Please take a look when you have a moment. 

    Melissa Kovach
    Melissa Kovach
    New Member
    June 23, 2026

    This is still an issue for me and my team. Sometimes components are not rendering correctly and it seems to be intermittent. Meaning, that one person can view the file and see things as intended while another user sees things jumbled. In my experience, when I first share my approved designs, everything looks right. But another day, they’re all jumbled. This has been a big issue for my design reviews - my clients can’t give feedback or sign off on jumbled layouts. And even worse, developers have started implementing based on these glitches and they show up in our product. 

    Like others, I can usually click into the component instance and everything resets. Although lately sometimes that doesn’t even work. 

    This is definitely NOT limited to components with slots. 

    Also, please don’t ask for access to my files. My client would never allow it due to NDAs and such. 

    Celyn_L
    Figmate
    Celyn_L
    Figmate
    June 24, 2026

    Hi ​@Melissa Kovach, thanks for taking the time to share these additional details.

    From your description, it sounds like different people can see the same file render differently, with component instances occasionally appearing jumbled until they’re selected or refreshed.

    I also completely understand your concern around sharing files due to client confidentiality and NDA requirements. That said, I’ve gone ahead and created a support ticket for you so the team can work with you directly to investigate further. Your ticket number is #1978890.

    Please keep an eye on your inbox for the next steps. Thanks! 

    Ben_Smeets
    Ben_Smeets
    Active Member
    July 5, 2026

    FYI, the issue still persists on our end as well. Not 100% reproducable. But the effect is common. Non updating components that use slots, until you click and select something inside the slot and/or need to copy paste the component (and/or user A seeing something completely different than user B).

    I hate to be the negative guy, but it feels like slots is going the Figma way of “almost… but no updates the next couple of years”…. shame.

    Damian_Summersall
    Damian_Summersall
    New Participant
    July 23, 2026

    Mine is also commonly seen in slots, and I can reproduce it pretty consistently with a particular component, if needed. I’ve attached a video. Happy to give access to an isolated file with the issue for reference too. 

     

    Celyn_L
    Figmate
    Celyn_L
    Figmate
    August 5, 2026

    Hi ​@Damian_Summersall, thanks for chiming in here and for taking the time to share a screen recording.

    It looks like the components configured to use Fill container are not sizing as expected and are stretching beyond their intended layout.

    I've gone ahead and created a support ticket so our team can investigate this further. Your case number is #2052140. I've also attached your screen recording to the ticket to help with the investigation.

    When you have a moment, could you please reply directly to the ticket with a link to the affected file and invite support-share@figma.com with "Can View" access? This won't impact your billing and will help us reproduce the issue and investigate it further with our Engineering team.

    For anyone else experiencing the same issue, please submit a bug report so we can investigate your specific setup.

    You can do this by going to the Support Hub, typing "Report a bug, contact agent", clicking Start a chat, and following the prompts.

    Please include:

    • A link to the affected file and grant "Can View" access to support-share@figma.com.
    • A short screen recording showing the behavior.

    Thanks! 

      Terms & ConditionsAccessibility statement