Skip to main content

The problem:
I have a hover button with 3 states - default/hover/active
When I add this component to my design and add a new interaction like “Swap Overlay” it takes several clicks to get it to swap overlays.

Now, this was working fine some time back and isn’t the case for everything.

I submitted this problem to customer support and, after giving them access to my files, they said:

“just make a panel with the default state. then, when hovering over the button, make it switch to the new panel with the hover state, and then click thru from there to swap the overlay”

And that sounded incredibly stupid. Afterall, this doesn’t actually solve any issues to what appears to be a bug.

So my question is: is this happening for others?

Hey ​@Alakazam, welcome to Figma Forum and thank you for taking the time to share this. I’m really sorry for the frustration here — I know how disruptive it can be when expected interactions don’t behave consistently.

A few updates on this and an ask for you:

  • I checked on your case, and it’s still open with our support team, who are reviewing the latest responses. I also came across a similar report around hover button behavior and have raised both threads with our product team for a closer look.
  • As they continue investigating, it would be really helpful if you could share any details about what seems to trigger the issue most consistently on your end (e.g. browser vs. desktop app, specific prototype setups, etc.). That kind of context helps us narrow down the variables and speed up the troubleshooting process.

We’ll share any broader updates here in this thread, and you’ll also receive account-specific developments by email from the support team. Thanks again for surfacing this and collaborating with us on the investigation.


It is also broken when looking at prototypes in the browser.

It seems like a random occurrence but mostly happens when a button has a hover state variation and I want it to also click through to open an overlay or navigate to another frame.

 

That said, the button to remove an interaction has also disappeared. The “remove interaction” tooltip appears when I hover over the blank area to the right side of the interaction where there was previously a button.

 

 

 


It is disappointing that Support just responds with Chatgpt suggestions that they don't bother to check and then respond with chatgpt pandering like 

"You're absolutely right that having to create separate frames for hover states adds unnecessary complexity"

it's no wonder it doesn't work.


Hey ​@Alakazam — thank you for taking the time to share more details on this unexpected behavior. I’m really sorry for the frustration it’s caused. Your case is still open with our Technical Quality team, and I’ve passed along the screenshot you provided to our engineering team for review. We’ll keep you updated as soon as any new details become available.