I used hover to create button hover states, but since today it no longer resets to its original state when I stop hovering. I can mimic the intended use by using mouse enter and mouse leaves, but until today hover worked.
It also doesn’t reset when you open an overlay, it’ll remain in its “hover” state forever, even when using mouse enter/mouse leaves.
Thank you its worked 🙂
Still having this issue
How is this still a thing! Come on Figma, this is basic interactions and its driving me mad!
I’ve tried using the ‘reset component state’ and options others have mentioned here.
This wouldnt be such a problem if I could also apply ‘change to’ to ‘this’ component within the component I’m in.
Please, Please, please fix this its 3 years old!
Also facing this issue. mind boggling this hasn’t been fixed more than 3 years later
but more frustrating is the fact there is not a single dev response here acknowledging this issue. I guess since Adobe didn’t buy you at the end, you decided to just be like Adobe>
Very disappointing
Same issue here.
When using the “mouse leave” workaround, all is well until I navigate to another page where the component is present. The component in question resets to the hover state upon navigation. I have to hover over it once more to reset it to normal. I wasted hours trying to fix this.
Super infuriating, especially when running usability tests 😕
Bumping - same things here…
I have this issue as well.
Bump. I’ve been facing this problem as well.
Same here. Quite annoying.
I’m not certain this is the same for everyone else, but, for me, it is always when I have a component with a hover state interaction nested in another component. Refreshing the prototype window doesn’t fix it. Work around? Use ‘on mouse enter/exit’ instead of ‘while hovering’. 🫤
We have the same issue, but it’s on ‘while pressing’ and opening an overlay.
FIGMA prototype: https://www.figma.com/proto/OOInghc3e8eBi3iAOD3zFE/Notices?page-id=47%3A1801&node-id=2458-15232&node-type=frame&viewport=-5030%2C2883%2C0.34&t=S47GhztUGHQYiLk9-1&scaling=min-zoom&content-scaling=fixed&starting-point-node-id=833%3A16668
I see multiple posts regarding this issue. The earliest one was back in year 2021. And now it is almost end of 2024. 3 years down the line and Figma cannot fix this issue? Not sure why the CONFIG & other marketing events are happening to promote Figma, but the team really need to look at the forums and make sure these type of critical issues are solved first.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
