👋🏻 Hi guys, I’ve run into what seems like a bug while working with the new slots feature in Figma components, and I’m curious if anyone else has experienced this.I’m currently implementing slots in my components and really like the concept so far. However, I’m facing an issue that makes the feature unreliable for my use case.The issue:Sometimes (not consistently), when I place a component with a hover interaction into a slot and preview the frame, the hover states inside that slot don’t trigger at all. Possible pattern I noticed:The issue seems more likely when using multiple slots within a single component For example, in a navigation bar with dynamic content on both the left and right sides (two separate slots), the hover states in the second slot often don’t work in previewAdditional observation:If I place placeholder elements (with hover states) inside the slot in the main component, those hover interactions usually don’t work When I then insert the component as an instance and add new elements into the slot, only the hover states of the newly added elements (inside the instance) work — not the ones defined in the parent componentThis behavior feels inconsistent and makes it hard to rely on slots for interactive components. Has anyone experienced something similar or found a workaround?Thanks in advance!

Hi everyone, thanks so much for your patience here.We’ve now rolled out a fix, and this issue should be resolved.Could you pleasetry the following steps to see if it resolves things on your end?Reload your tab or Figma clientFor any problematic slots, try regenerating the affected instances or clicking into them to refreshThese should update the instances and help apply the fix.If you’re still seeing the issue after trying this, feel free to share a quick screen recording and wecan take a closer look🙌

Josua

New Member

Solved

Some elements in a slot do not show hover state in prototype preview

Forum|Forum|6 months ago
March 21, 2026
21 replies
519 views

👋🏻 Hi guys,

I’ve run into what seems like a bug while working with the new slots feature in Figma components, and I’m curious if anyone else has experienced this.

I’m currently implementing slots in my components and really like the concept so far. However, I’m facing an issue that makes the feature unreliable for my use case.

The issue:
Sometimes (not consistently), when I place a component with a hover interaction into a slot and preview the frame, the hover states inside that slot don’t trigger at all.

Possible pattern I noticed:

The issue seems more likely when using multiple slots within a single component
For example, in a navigation bar with dynamic content on both the left and right sides (two separate slots), the hover states in the second slot often don’t work in preview

Additional observation:

If I place placeholder elements (with hover states) inside the slot in the main component, those hover interactions usually don’t work
When I then insert the component as an instance and add new elements into the slot, only the hover states of the newly added elements (inside the instance) work — not the ones defined in the parent component

This behavior feels inconsistent and makes it hard to rely on slots for interactive components.

Has anyone experienced something similar or found a workaround?

Thanks in advance!

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 to see if it resolves things on your end?

Reload your tab or Figma client
For any problematic slots, try regenerating the affected instances or clicking into them to refresh

These should update the instances and help apply the fix.

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 🙌

Ant.Scalf

New Member

I’m running into the same issue. I created dropdown menu items within a slot container, but the hover states aren’t being applied to those items.

Daan Steegmans

New Member

Same issue here

MiLe

New Member

+1

Oliver Woods

New Member

+1

Celyn_L

Figmate

Hi @Josua and others following along — Celyn from Figma Community Support here.

Thanks everyone for flagging this and for sharing the detailed context around the hover state behavior within slots — that’s really helpful.

I’ve raised this with our internal team so they can take a closer look at this. I’ll follow up here as soon as I have more insights to share.

Appreciate everyone’s patience in the meantime 🙏

Celyn_L

Figmate

Hey everyone — thanks for your patience while the team looked into this.

This doesn’t appear to be expected behavior, and we’d like to take a closer look.

Could you please submit a bug report from within Figma? You can do this by clicking the question mark icon in the bottom-right corner and selecting Contact support, or via the Support Hub:
Start a chat → type “Report a bug.”

When you have a moment, please also share the impacted file with support-share@figma.com and grant “Can View” access — this won’t impact your billing and will help us reproduce the issue and investigate further with our Engineering team.

After you’ve submitted a report, feel free to share your case number here. I’m happy to help surface it internally to increase visibility.

Really appreciate you taking the time to report this and help us dig into it — we’ll keep an eye out for your report 🙏

gleemodus

New Member

Ticket number. 1826503

It maybe an issue of using component with slots inside of slots in design layouts or another component.

Cale Jr

New Member

I have the same problem with a select dropdown menu using slots. At first the hover works on a fresh instance, but if I add an onclick to one of the menu items it stops working, and if I remove the onclick it doesn’t come back (weird). I also had another instance where it stopped working when I changed the text inside the menu item.

Karl Kipper

New Member

+1

Multiple slot components with hover states seem not to work

Celyn_L

Figmate

Hi @Cale Jr @Karl Kipper — thanks for flagging this.

As mentioned above, could you please submit a bug report from within Figma? You can do this by clicking the question mark icon in the bottom-right corner and selecting Contact support, or via the Support Hub:
Start a chat → type “Report a bug.”

When you have a moment, please also share the impacted file with support-share@figma.com and grant “Can View” access — this won’t impact your billing and will help us reproduce the issue and investigate further with our Engineering team.

After you’ve submitted a report, feel free to share your case number here. I’m happy to help surface it internally to increase visibility.

Thanks!

Show more replies

Sign up

Login with SSO

Login to the community

Login with SSO