👋🏻 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 🙌

Show previous replies

Rubem_Pechansky

Active Member

I also have stumbled into this in a recent project. Because of those problems I decided to give up using slots in some frames. But there is also another problem, maybe they are related. Some contents inside auto-layout slots refuse to resize themselves in prototype mode. I’ve just submitted ticket #1834908 and shared the file with support-share@figma.com as described above.

djv

Community Support

Hi @Rubem_Pechansky, thanks for chiming in here!

I completely understand your frustration with this. I’ve confirmed that the team has received your ticket and file share, and I’ve escalated your ticket on your behalf so they can investigate this for you on priority.

The team will review and be in touch as soon as possible.

Miles Roxas

New Member

has this been resolved? Still not working for me...

Tom Reem

Figmate

Hey @Miles Roxas — thanks for adding your experience here, and sorry to hear this is affecting your workflow, too.

I checked in on this and our Engineering team is still actively investigating. To help move things along, it would be really useful for us to look at a specific file where this is happening. I've sent you an email with next steps on sharing access securely. If you're able to provide that, it would go a long way. Check your inbox for your case number: 1845148, and we'll go from there. 🙏🏻

If anything else comes up, don't hesitate to reach out.

Rubem_Pechansky

Active Member

I also have stumbled into this in a recent project. Because of those problems I decided to give up using slots in some frames. But there is also another problem, maybe they are related. Some contents inside auto-layout slots refuse to resize themselves in prototype mode. I’ve just submitted ticket #1834908 and shared the file with support-share@figma.com as described above.

Follow-up: this specific issue is probably fixed. For those who have this problem, you’ll have to run the command “Regenerate All Instances” from Actions, then edit or add something just to save your Figma file. After that, the problem seems to be gone. Hope this works for you guys too.

Celyn_L

Figmate

Hey @Rubem_Pechansky, really appreciate you taking the time to share this workaround.

I’m glad to hear that resolved it on your end, I’ll pass this along to the team as well.

If anyone else is still encountering this issue after trying this, feel free to share a file link so we can take a closer look.

Thanks again for sharing this 🙌

Etienne Barbedette

New Member

Same issue here… doesn't seem to have been resolved

adamsmasher

Figmate

Hi, @Etienne Barbedette - thanks for posting, and sorry to hear that you’re still seeing this.

I just checked again on our end and it looks like the fix isn’t out yet. While I don’t have a specific ETA for the release of it, you might want to try the suggested temporary solution by @Rubem_Pechansky from earlier in the thread as that seems to have helped in the interim:

Follow-up: this specific issue is probably fixed. For those who have this problem, you’ll have to run the command “Regenerate All Instances” from Actions, then edit or add something just to save your Figma file. After that, the problem seems to be gone. Hope this works for you guys too.

Thanks for your patience!

Etienne Barbedette

New Member

I tried, but it didn’t work for me.

djv

Community Support

Thanks for following up, @Etienne Barbedette!

I appreciate your patience here. I can see how this issue is disrupting your workflow, especially with the temporary solution not working as expected for you. I understand how frustrating that can be.

Our team is still actively investigating and working toward a proper fix. As soon as it’s available, we’ll share an update right away.

Thanks again for sticking with us while we get this resolved.

Show more replies

Sign up

Login with SSO

Login to the community

Login with SSO