New Participant

Solved

Components with mouse interactions revert to default variant state, but only when logged in

Forum|Forum|8 months ago
January 13, 2026
22 replies
774 views

My components with "while hovering" and "while pressing" variants (and interactions) are reverting back to the default values and icons when I'm interacting with them. I've tried viewing the prototypes within the Figma desktop app, as well as on Firefox, and on either cases this issue persists.

Weirdly though, this only happens if I'm logged into Figma. If I view the same prototype in Private/Incognito browser window, this issue doesn't occur.

Figma Version: Figma Desktop App version 125.11.6
Operating System: MacOS Tahoe 26.1

Preview:

This topic has been closed for replies.

Best answer by Celine_

Hey everyone, thanks for your patience while our engineering team looked into this.

They investigated the issues reported by @Lucy_Hill and @Alexandra Vega (thank you for submitting bug reports!), confirmed this was a bug, and have now released a fix. Please refresh your tabs and try again. Things should be working as expected now.

For others, if you’re still running into issues, please follow these steps so the team can take a closer look:

Share edit access to the affected files with support-share@figma.com. This is our official Support account, and only select Support and Engineering teams will be able to access the files for investigation. You won’t be charged for this.
Submit a help ticket here and include direct URLs to the files you’ve shared.
Once that’s done, let me know and I’ll make sure your ticket is escalated for review. Thank you!

Show previous replies

Kaarel

New Member

Any updates on this Figma? This has been ongoing for whole week soon. How do I solve this?

Celine_

Community Support

Hi everyone, Celine from Figma here! Thanks everyone for flagging this and for sharing examples. I can see how disruptive this is, especially since it’s affecting multiple interaction types (hover, press, boolean props) across different files.

The fact that this only happens when you’re logged in (and not in an incognito/private window) is especially helpful context and suggests this will need a deeper investigation to reproduce and understand what’s happening here. In the meantime, could you also check whether the issue occurs in other browsers? Our supported browsers are Chrome 99, Firefox 101, Safari 16, Microsoft Edge 121 or later.

To make sure our support team can properly dig into this, the best next step is to reach out to them directly so they can review the affected files.

You can do that via our Support Hub here:

Go to the Support Hub
Type your question
Click Start Chat, and type ‘Report a bug’ .The chatbot will help you open an email case with our Support team.

Once submitted, the Support team can investigate further and loop in engineering as needed. Thanks again for taking the time to report this, it really helps us understand the scope of the issue.

Alexandra Vega

New Participant

Hello @Celine_ , for me it’s like this with the browsers:

Figma Desktop app ❌
v125.10.8 Issue
Chrome window ❌
v143.0.7499.193 - Issue
Chrome Ingonito/Private window✅
v143.0.7499.193 (logged out) - Works fine
Microsoft Edge✅
v143.0.3650.139 (logged out) - Works fine
Firefox ✅
v147.0 (logged out) - Works fine

I have submitted the ticket and waiting for the response, if I manage to solve it I’ll try to post back here.
Thanks for reaching out to us Celine

Lucy_Hill

New Participant

Hi @Celine_
for me with browsers it’s like this:

Chrome window - logged in - Issue
v.143.0.7499.193
Chrome incognito - logged out - works fine
v.143.0.7499.193
Chrome incognito - logged in - Issue
v.143.0.7499.193
Safari - logged in - Issue
v.18.6
Firefox - logged out - works fine
v.147.0.1
Firefox - logged in - Issue
v.147.0.1

I have also submitted a ticket and waiting for the response. Thanks for reaching out to help Celine

Anu Ojoawo

New Member

I’m experiencing this exact issue.

Nwafor Charles

New Member

I’m experiencing this too, especially with the hover effects of my components.

Celine_Solution

Community Support

Hey everyone, thanks for your patience while our engineering team looked into this.

They investigated the issues reported by @Lucy_Hill and @Alexandra Vega (thank you for submitting bug reports!), confirmed this was a bug, and have now released a fix. Please refresh your tabs and try again. Things should be working as expected now.

For others, if you’re still running into issues, please follow these steps so the team can take a closer look:

Share edit access to the affected files with support-share@figma.com. This is our official Support account, and only select Support and Engineering teams will be able to access the files for investigation. You won’t be charged for this.
Submit a help ticket here and include direct URLs to the files you’ve shared.
Once that’s done, let me know and I’ll make sure your ticket is escalated for review. Thank you!

Lucy_Hill

New Participant

Hi @Celine_

Thanks to you and the engineering team for looking into this and fixing the bug. It looks to be working fine for me now.

Alexandra Vega

New Participant

Hi @Celine_
Thank you and the team for the effort into fixing this.
It seems to work be working as usual now.

Celine_

Community Support

Glad to hear it’s working now, thanks for confirming!

Show more replies

Sign up

Login with SSO

Login to the community

Login with SSO