Just ran into this issue. To see it’s been an issue for this long is disconcerting. Does anyone know if this goes away if you use the prototype for site creation?

Alright, then what is the “while hovering” option for?

Jk, I get that many here just need their pt to work and these workarounds may get a good dose of appreciation. Kudos to those who provide them.

Allow me to rant for those of us who just want things to work the way they’re supposed to, though.

thanks, this worked for me.

Still quite annoying

Years into this thread. Still hopelessly broken.

At times, it seems to be related to nested components (which have always caused as many issues as they solve). However, even if you detach the parent level in nested components, they still seem to retain residual linkages that totally foul up the hover interaction.

Same issue here!

Until they fix it, the best workaround I’ve found is to close the prototype tab/window and open it again.

Same issue. It’s really rough.

Figma doesn’t seem to fix any of these bugs, nor update the variables panel. Nothing. It’s like they don’t care and they have to put AI instead of making the UI and the prototyping work properly. (Shrugs)

worked fine so far, now stuck all the time. really annoying and difficult to work with.

Hey All, thanks for flagging this and apologies for the lack of acknowledgement here!

This topic was created 3 months before I joined Figma, and during that time, the forum was primarily run by the community.

If none of the suggested workarounds above fix the issue for you, your best option would be filing a bug report with support directly, as mentioned by @Fernando_Lins.

You can submit a bug report to our support team directly via the form here: https://help.figma.com/hc/en-us/requests/new?ticket_form_id=360001744374

Please use your Figma account email, include a link to the file, and share edit access with support-share@figma.com, so the team can take a closer look at how you’ve set up your prototype.

I am still experiencing this problem and have opened a support ticket with Figma as instructed above.

Thanks, Ashley!

I can confirm that support received your ticket #1121621 and recently replied to you.

Please check your inbox and continue working with support.

I’m having this issue. @Kolodziej_Ashley did your issue get fixed? Could you share the solution with us? I can’t send my file to Figma support due to company policy.

There was no solution - they are aware of the issue and there is no timeline due to the complexity of the issue.

I’m having this problem now. I thought it was an overlay issue. But the workaround I did was by having my button components inside my local components. I think the issue is with the Published libraries or having the components outside your local ones especially if you have so many components in a project. It’s not a fix tho.

I have had the same issue many times already. I can’t believe this is a persistent bug for over 3 years now… Fix this.

Same issue

And it seems to be getting worse 

Would appreciate this getting fixed

I think i kinda found the solution. To solve this issue you need to replace one «hover» interaction with «mouse enter» and «mouse leave» interactions inside of master component. 

The example below is very simple but this also worked in a much more complex prototype with components added from library
 

Still happening in 2025.  Any idea when you’ll actually fix this, Figma?

Going on 4 years with this bug. Seriously affects user testing of prototypes with actual clients. Long lists with hover states regardless if I use while hovering or on mouse enter and leave. 

Also, for anyone trying mouse enter/leave that isn’t a fix. It creates more work and another set of problems if you layer a hover inside another hover (a grid row with background hover and a button inside the row with it’s own hover).

Agreed that this is a huge fail that the issues still exists.

it also exists when doing mouse enter and mouse leave.

but mouse enter/leave is most definitely a much more appropriate way to do do hover states. While hovering is great if you want to show something like a tooltip or popover, literally while hovering.

but state changes are absolutely more better when do e with enter/leave. Reasoning is obvious when you read that.

Sad that this issue and many more like it are not addressed

you ever try turning off “show dimensions on objects” in the preferences? Next time you open the file that setting is back again. Figma has zero persisting of user choices. Zero! But that is a different soapbox.

I think i kinda found the solution. To solve this issue you need to replace one «hover» interaction with «mouse enter» and «mouse leave» interactions inside of master component. 

The example below is very simple but this also worked in a much more complex prototype with components added from library
 

 

 

Appreciate your effort on this, but this is actually what everyone was dreading on as a workaround for the past almost 4 years. Don’t get me wrong, this is a great workaround. It’s just that it’s not new to us and would be a lot or work for other scenarios like hovering on tabs or table headers. Still, thanks for sharing.

This still happens to me. “Closing and reopening the prototype helps solve the problem.
But after some time, the bug may appear again.” 
It’s very annoying when I’m presenting or conducting usability test. I can’t just keep refreshing

Adding my humble upvote to please fix this 🥲

This is a particularly frustrating bug. When demoing prototypes to product owners, stakeholders, and users, it creates the impression that the UX designer is either overlooking key details or lacks expertise—which can undermine trust in the design process. Figma, this feels like a major issue. It's surprising and disappointing that it's been reported for so long without resolution.

I have the same issue, and I am confusing everyone with my prototype.  Seems like a basic fix. Figma seems to have a lot of issues in prototype mode!