Skip to main content
Question

Repainting slots

  • April 21, 2026
  • 3 replies
  • 31 views
Zach7

I’ve found slots incredibly buggy right now unfortunately. I love the idea, but they’ve been rather frustrating lately.

I’ve had two bugs that seem related I have repeatedly had, but am unable to set up a test file for these.

 

Slot sizes not adjusting

Something like this hierarchy. Despite the fact the two components are bound in an autolayout with gutter, it doesn’t seem to paint properly. I often have to double click the children components individually.

Component >

↪ Slot

↪↪  Rows [Autolayout]

↪↪↪ Row [Autolayout]

↪↪↪↪ [Component]

↪↪↪↪ [Component]

 

Slot content not refreshing

Sometimes a colleague uses my account on their computer to check something. When checking an instance of a component with a slot, sometimes they see the default content and not the content I’ve put in there. Despite it being saved. I have found no solution for this except detaching the instance.

 

3 replies

Celyn_L
Figmate
  • Celyn_L
  • Figmate
  • April 23, 2026

Hi ​@Zach7, Celyn from Figma Community Support here.

Thanks for sharing this in detail and for the screenshot, that’s really helpful. From what you’ve described, it sounds like you’re running into two recurring behaviors with Slots:

  • In a nested Auto Layout setup, Slot content doesn’t always render or size correctly unless you manually click into the child components
  • In some cases, when your colleague accesses the same instance from another computer (using your account), they see the default Slot content instead of the saved overrides

I’m going to double check both of these with the team to better understand what’s expected here.

I know this has been difficult to reproduce in a separate test file, but if you’re able to capture a short screen recording the next time either issue happens, that would really help us take a closer look.

For the second issue, could you also confirm whether you and your colleague are using the same environment, or different ones (for example, browser vs desktop app)?

I’ve also noted that detaching the instance has been your only reliable workaround so far, and will pass that along as well.

Thanks again for taking the time to document all of this, I’ll follow up here as soon as I have any updates to share.

Zach7
  • Zach7
  • Author
  • New Member
  • April 24, 2026

I know this has been difficult to reproduce in a separate test file, but if you’re able to capture a short screen recording the next time either issue happens, that would really help us take a closer look.

If I see it again, I’ll record it. I’m no longer working on that file as it was in a client’s environment.

For the second issue, could you also confirm whether you and your colleague are using the same environment, or different ones (for example, browser vs desktop app)?

Both using MacOS Desktop App.

Thank you!
 

Celyn_L
Figmate
  • Celyn_L
  • Figmate
  • April 24, 2026

Thanks for confirming ​@Zach7, that’s helpful to know you’re both using the macOS desktop app.

Got it on the recording as well - appreciate you being open to recording it if it comes up again.

I’ll continue checking this with the team on my end and I’ll follow up here as soon as I have any updates to share 🙌

Terms & ConditionsCookie settingsAccessibility statement