Question

In prototype mode, the hover effect ("while hovering") sticks and does not disappear

Forum|Forum|5 years ago
May 11, 2021
77 replies
19995 views

In prototype mode, the hover effect (“while hovering”) sticks and does not disappear after hovering over an element. As a result, when hovering over several objects, all hover effects remain on the screen. What is the bug? : worried:
Closing and reopening the prototype helps solve the problem.
But after some time, the bug may appear again.
It looks like some kind of memory problem, in general, prototypes and files take a long time to load and sometimes slow down. It’s very unpleasant to work. In Figma via macOS app

Ask the community

This topic has been closed for replies.

Show previous replies

P

p_g

I have the same bug that just appeared now, everything was working just fine, and then bang.
Are there any Figma support person even reading this topic??
When is this going to be fixed???
Please help us designers, because showing this to clients is a bad image on us and on you FIGMA 😛

Marie_Tamliani

same issue, it’s crazy how it still not got fixed.

Fernando_Lins

New Participant

The forum might be read by Figma support but what actually works is submitting a bug report and getting everyone else with the same issue to submit it too.

Issue still persists

Thanks to Agni_Kaster, I was able to successfully apply the fix and would like to share it here in this thread. Here’s what you need to do to make this headache go away:

Make a copy of your default state. Animate your “while hovering” variant to the new copy of your default and set it to the ‘mouse leave’ option in the animations DDL (a section above where “after delay” setting).

Hopefully there will be a fix in the near future but hope this helps somebody!

kmh

New Member

It’s also not viable. I have a data table populated mostly with components. It would take dozens of local copies just to populate the five sample rows.

The worst part is the sample data table is part of a design system test! It’s going to be very hard to explain this is a Figma bug and not a design system bug.

JoeM

New Participant

Why is this still an issue? Have Figma not provided an official workaround for this, at least? Are we not using the logic properly? @Josh, this has been an issue for years now and is pretty essential in terms of prototyping concepts for a client.

There are threads full of people complaining about it back to 2020-2021. 🤯 🤯 🤯 🤯 🤯 🤯 🤯 🤯 🤯 🤯 🤯