Skip to main content
Milorad
New Member
March 24, 2026

Fix Slots!

  • March 24, 2026
  • 21 replies
  • 1139 views

Just fix slots! 

The slot feature doesn’t behave properly when switching variants: around 90–100% of the content from the other variant simply disappears.

21 replies

Christina Kuo
New Member
April 15, 2026

Hi ​@AskDave 

Thanks for getting back to me. I just submitted a bug report (#1850172) with the file URL and a screen recording. I hope this will help, and I look forward for new updates!

Thanks

AskDave
Active Member
April 15, 2026

Good morning ​@Christina Kuo 

 

Thanks for that, Someone from our support team will be in touch with you shortly to help. Really appreciate your patience in the meantime!

 

Thanks,
Dave

Jason Vail
New Member
April 17, 2026

I’m seeing the same thing. What’s more troubling is that when you click into the design it seems to self fix. But only for you and when you return it’s still an issue. I’m having to traverse deep into a design and make changes to get it to update properly. Difficult to know when you have actually fixed though. 

 

Christina Kuo
New Member
April 21, 2026

Hi ​@Jason Vail 

I found another comment about this issue at 

I have reported a bug issue for this topic. The latest update is that Figma will be rolling out an update in a week or two! Hope this help :) 

djv
Figmate
Community Support
April 21, 2026

Hi ​@Jason Vail and ​@Christina Kuo

I’ve merged your topic into this one to keep things in one place. We’ll provide an update in this thread from the team as soon as we get word on the progress for the fix. We appreciate your patience and understanding in the meantime. 

Noah Mittman
New Member
May 18, 2026

I’m also seeing this bug. Components in slots rarely display with their settings/variants properly applied on document-open, and will not paint properly until the frame/instance is directly selected. Which means one must select every instance individually for all of them to correctly display in the file.

It seems to happen primarily on component instances in slots that are not part of the initial slot definition.

 

Example: a component with a slot that has two sub-components in the slot by default.

An instance of this component with a change on one of those two sub-components generally displays fine on open.

An instance of this component that has been modified to have a third sub-component with variants will typically have this third sub-component not pick up its correct variant on open, and not pick it up correctly until the modified instance is selected/entered

d_greg
New Participant
May 19, 2026

Hi, Slots are in Beta, that means don’t expect too much. On the other hand I’d like have Slots be quite flexible on overriding the AutoLayout direction/orientation (row or column). I noticed that in some cases I need to design something that requires two buttons:

[Button][Button] (inside the Slot with horizontal direction - row)

But sometimes need to use the same “parent” component with Slot, and have the buttons being stacked (e.g. on mobile breakpoint)

[ Button ]
[ Button ]


As soon as I fix the Slot auto layout behavior and properties, there’s no way to override it and I have to create new variants and show/hide toggles

LisaMichelle
New Participant
June 19, 2026

Hello, does anyone know if slots has been fixed now? I used it for a while, but it was buggy (content kept disappearing when trying to edit slot content)

I am trying to improve my new libraries and wondering if I can try slots again or should skip for the coming time.

Kerry_Johnson
Active Member
June 24, 2026

Hi, Slots are in Beta, that means don’t expect too much. On the other hand I’d like have Slots be quite flexible on overriding the AutoLayout direction/orientation (row or column). I noticed that in some cases I need to design something that requires two buttons:

[Button][Button] (inside the Slot with horizontal direction - row)

But sometimes need to use the same “parent” component with Slot, and have the buttons being stacked (e.g. on mobile breakpoint)

[ Button ]
[ Button ]


As soon as I fix the Slot auto layout behavior and properties, there’s no way to override it and I have to create new variants and show/hide toggles

 

Not only am I noticing that caveat, but slots seem to go out of sync in a nested subcomponent instance setup.  Consider the following setup:

 

Table (Component)

  • Table Header (Slot)
  • Table Body (Slot)
    • Table Row (Layer)
    • Table Row (Layer)
      • Table Cell (Subcomponent) x 8
        • Table Cell Content (Slot)

 

One would expect that autolayout changes to “Table Cell Content (Slot)” in the master Table component to propagate - if not immediately, then maybe after selecting “Reset slot” or “Reset instance” on “Table Cell (Subcomponent)” and/or “Table Cell Content (Slot)” of the Table component instance.  Out of frustration, you might even reset “Table Body (Slot)”… but no go.

Unfortunately, it seems the only way for me to get “Table Cell Content (Slot)” to take in the changes is to reset the whole Table component instance.  As you can imagine, this is a huge PITA in a table of many rows.

I don’t know if this is a bug or limitation of slots.  It feels like a bug, because why would the slot of a nested instance lose track of its own changes just because it’s an instance?

Jeff
New Participant
July 31, 2026

Hello all.  Im having the same issue.  slots with other complex components are dissappearing when editing the slot’s content.