Skip to main content
Luongnd
Active Member
September 24, 2024
Question

Interactive state doesn't reset after overlay is closed

  • September 24, 2024
  • 30 replies
  • 2053 views

Yes I know this topic has been raised before, but I would like to raise it again, since it is breaking the core interaction in my design system. Is Figma even aware of this issue? Since the last discussion about it is ~2years ago, and this issue still exists.

Steps:

  • Create a Button component set with 2 variants: Default, On Press
  • Add interactions in the variant: “Default” → While pressing → Change to “On Press”
  • Insert an instance of the “Default” button into a new Frame
  • Add interactions to the button: On Click → Open overlay. Check the “Close when clicking outside” box.
  • Test the prototype

Results

  • When you click the button, the button change to “On Press”, the overlay opens, but when clicking outside the overlay to close it, the button does not reset back to “Default”.

Expected:
The button should reset to “Default”.

30 replies

Gkotik
New Member
September 30, 2025

Please fix it, have the same problem

Giorgito
New Member
October 2, 2025

Same issue here, please do something!! 

 

Airwrecka
New Participant
October 9, 2025

I had to remove the interaction “while pressing” on our link component, because it stuck after opening and closing an overlay in our prototype. But good to know, I am not the problem...

Nicholas_Kaschak
New Member
November 5, 2025

Same issue here, posting for visibility!

djv
Figmate
Community Support
November 5, 2025

Hey All, thank you so much for continuing to flag this issue and for your patience as we work through it.

 

I’ve shared this topic with our team, and they confirmed that it’s a known, long-standing bug they’ve been investigating since it was first reported back in January 2022.

 

While I don’t have a specific timeline to share at the moment, I completely understand how frustrating this has been—especially with more users running into the same problem recently. Please know that we’re doing our best to advocate for a fix and to keep this on the team’s radar.

Luongnd
LuongndAuthor
Active Member
November 17, 2025

Hey All, thank you so much for continuing to flag this issue and for your patience as we work through it.

 

I’ve shared this topic with our team, and they confirmed that it’s a known, long-standing bug they’ve been investigating since it was first reported back in January 2022.

 

While I don’t have a specific timeline to share at the moment, I completely understand how frustrating this has been—especially with more users running into the same problem recently. Please know that we’re doing our best to advocate for a fix and to keep this on the team’s radar.

Thanks for letting us know. We look forward to the fix!

Designerd
New Member
December 19, 2025

Is there another method that the community can use to report this issue, other than forums? It seems that without a sustained, continued, press on the subject, it may not get addressed...

Lennard_Brauner
New Member
February 4, 2026

Please try this method:

Create a Component of the Button.

 

Prototype Button:

Default → Hover
While Hovering

Default → Pressed
While Pressing

Pressed → Default
After Delay: Change to Default.

 

Use an instance of it to oben the Overlay → Close clicking outsinde.

 

The Button Should be pressed as long as the overlay is opend. 

After closing the delaytime begins and the button change to its default state.

 

For a larger design system, you might need to create an extra "Overlay Button" that automatically reverts to the default state.

 

Hope thats a usecase...

stevekulaga
New Member
February 11, 2026

Same. The hack that Lennard recommended does work, but it isn’t a great solution because there is still some interaction of the component that isn’t how it actually should be when being developed and could lead to confusion. Plus adding another interaction in a large design system isn’t ideal if it isn’t necessary. Please fix this Figma! 😩

Waldo
New Participant
February 27, 2026

Fascinating topic, Google lists this thread for the exact problem. I’ve been two hours clicking prototype buttons, and this reveals I was not crazy nor doing something wrong. 

It’s somewhat of a corner case, however, it is a bug