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

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.

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

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

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

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

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

Feels like a total bug.

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.

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)?

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 🙌

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

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.

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

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 👍

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 :)

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.

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

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

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 🙏