Skip to main content
Solved

components inside slots are very buggy and keep showing the original nested component color variable

  • August 5, 2026
  • 3 replies
  • 57 views
AlBara Adel

Hi everyone,

I’m facing an issue with the icon behavior in my designs, I have the original Icons as components with a set color variable.

When using them inside other components (nested) and changing their color variant, everything works perfectly, but then without me touching them they switch to showing the original color of the icon component in the view.

the actual variable selected is preserved and correct, so it doesn’t actually like switch back to the original variable, it will say that it’s using icon-black for example, but in the viewport it will be showing icon-blue and even the stroke width variable is not applied while showing the setting is correct.

I don’t know if this bug is related to slots, I’ve been using them heavily lately.

also just duplicating the component will create a fixed one.

sometimes undoing some of the other changes in the page (no one touched the actual component with the issue) it fixes itself.

even like deleting it and leaving figma for a minute and then undoing the deleting sometimes fixes it.

it’s very annoying.

thanks.

Best answer by Gayani_S

Hey ​@AlBara Adel, thanks for testing that out and letting me know!

I still don't have a confirmed root cause or a timeline to share. Slots are still in open beta, so bugs like this can show up. And the way you described it fixing itself (after an undo, a delete-and-undo, or just stepping away for a minute) tells me this is about the canvas not staying in sync with what's actually stored. It's not something wrong with your variable setup.

Here's what I’d recommend:

  1. Open a request through the Support Hub and attach a duplicate of the file where this is happening.
  2. If you can, include a short screen recording showing the mismatch (properties panel vs. canvas).
  3. Let them know whether the color change happens because you're manually switching the icon's variant inside the slot, or because something else (a variable or mode change) is switching it automatically.

 

Thank you, 

Gayani 

3 replies

Gayani_S
Figmate
  • Gayani_S
  • Community Support
  • August 6, 2026

Hey ​@AlBara Adel, thanks for reaching out!

The properties panel showing the correct variable (icon-black) while the canvas renders something else (icon-blue), and that the stroke width variable doesn't apply either, points to the canvas not staying in sync with what's actually stored, rather than anything wrong with your variable setup.

One thing worth trying next time it happens: run Regenerate all instances (slow) from Quick Actions (Cmd/Ctrl + /, then search for it). It forces every instance in the file to re-render, and it's the standard fix for this kind of mismatch. It may save you the duplicate/undo/delete dance you've been doing.

Quick question so I can point you to the right info: when the color changes, is that because you're manually switching the icon's variant inside the slot, or is a variable or mode switch automatically changing which variant/color shows? If it's the latter, there's a documented limitation where nested instances don't always carry their overrides through a variable-driven variant change, and our guide on Use slots to build flexible components in Figma has a more reliable pattern for binding colors in that case. If it's the former, this is likely more specifically about instances inside slots, which is an area we're continuing to look into.

Either way, I don't have a fix or timeline to share yet, but I don't want you to think this is something wrong on your end. If you'd like us to take a closer look with file access, you can reach out through the Support Hub with a duplicate of the file.

Let me know how the quick action goes, and what your setup looks like, happy to dig further from there! 

AlBara Adel
  • AlBara Adel
  • Author
  • New Member
  • August 27, 2026

One thing worth trying next time it happens: run Regenerate all instances (slow) from Quick Actions (Cmd/Ctrl + /, then search for it). It forces every instance in the file to re-render, and it's the standard fix for this kind of mismatch. It may save you the duplicate/undo/delete dance you've been doing.

Hey Gayani,
I tried the suggested fix and it doesn’t actually fix the issue, the icons don’t turn back to their correctly assigned variables.

Thanks.

Gayani_S
Figmate
  • Gayani_S
  • Community Support
  • Answer
  • August 27, 2026

Hey ​@AlBara Adel, thanks for testing that out and letting me know!

I still don't have a confirmed root cause or a timeline to share. Slots are still in open beta, so bugs like this can show up. And the way you described it fixing itself (after an undo, a delete-and-undo, or just stepping away for a minute) tells me this is about the canvas not staying in sync with what's actually stored. It's not something wrong with your variable setup.

Here's what I’d recommend:

  1. Open a request through the Support Hub and attach a duplicate of the file where this is happening.
  2. If you can, include a short screen recording showing the mismatch (properties panel vs. canvas).
  3. Let them know whether the color change happens because you're manually switching the icon's variant inside the slot, or because something else (a variable or mode change) is switching it automatically.

 

Thank you, 

Gayani 

Terms & ConditionsAccessibility statement