Skip to main content
Yulia
May 11, 2021
Question

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

  • 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

This topic has been closed for replies.

77 replies

A.J_Kandy
May 11, 2023

It’s nearly mid-2023. This is still happening.

How are we supposed to produce clickable prototypes that we can show to clients / colleagues if these basic, basic things aren’t reliable?

I can mock things up in CSS directly in CodePen, but I can’t really share that with collaborators.

Honestly, it’d just be nice to have a set of basic, consistent HTML/CSS-standard web forms elements, so we 1) don’t have to reinvent them from scratch with every project and 2) don’t have to fake them with rectangles and “states” like we used to do in the early 2000s with imagemaps.

Danilo_Tumminello
May 17, 2023

No resolutions or tips on this? I was wondering what I was doing wrong - Quite basic bug and should be fixed

June 1, 2023

The problem is very much alive and well!
Can anyone recomand an alternative to Figma?

Morten_Christopher_Solem
June 27, 2023

Still an issue! Hey Figma, please fix this 😢 At least, please give us an update, tell us that you’re working on it (if you are).

It’s super annoying and also makes user testing a bad experience

July 25, 2023

I am also having this issue when there are multiple interactions on hover. If i only have 1 interaction then it is working, but that won’t work for what i need. Mouse enter/leave also don’t work.
On hover → change to hover state & open overlay

Jake_Ledford
August 11, 2023

Still same issue. Why isn’t this fixed when this thread was started over 2 years ago?

Tom_Parandyk
August 17, 2023

Solved. 🫣
The best workaround is to wrap the interactive component at the point of use in an extra frame and instead of attaching the on click interaction directly to the component, attaching it to the extra frame.

Steps to apply the fix:

  1. Create a master component with at least 3 states:
    a. Regular
    b. Hovered
    c. Selected
  2. Link the “Regular” state with “Hovered” using the “while hovering” interaction
  3. Add the instance of the component to your layout
  4. Wrap the instance in a frame
  5. Add “on click” interaction to the wrapping frame, not to the instance, that links the component with the target frame
  6. In the target frame use the “Selected” state for the instance

The selected state will remain selected on the target frame after navigating the prototype
🙂

Chris_Boggs
New Member
September 12, 2023

Everyone in my org is experiencing this too. Screws up our user tests since interactive components don’t render as they ought to. None of the suggested fixes work for us and seem like unnecessary workarounds anyway.

Molly_O_Riordon
September 12, 2023

Variables are cool, but echoing everyone else here: we really need these basic, essential things fixed.

Prouvost_Nicolas
New Participant
September 15, 2023

Thanks for sharing. Not working for me, even with the “wrapping” trick.

Think they broke that when they revamped the state management.
That used to work perfectly well before, and I have an old proto using the old state management that works fine.

Any update from Figma on this problem? Thanks!

My use case:

  • I have cards components with three states: default, hover, selected
  • from the components themselves, I link the default state to the hover state while hovering
  • from the screen, I have an instance of my component that I link to another screen on click
  • The on click is not working, even if I wrap the component in a frame

NB I tried nearly all the workarounds listed, nothing works… Driving me mad.
This is really basic stuff.