Skip to main content
Solved

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

  • January 13, 2026
  • 22 replies
  • 475 views

driftingsteps

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:

 

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!

 

22 replies

Todd_Coleman
  • New Participant
  • January 13, 2026

I am having a very similar, if not exact, problem.
 

 


Lucy_Hill
  • New Participant
  • January 13, 2026

I am also having this same problem, with nested components only for mouse enter and mouse leave interactions. Also having a similar issue with switching boolean props on/off causing overrides to be reset.


Alexandra Vega
  • New Participant
  • January 13, 2026

Hello, I am having the exact same problem with while hovering, on click, and boolean interactions, the overrides keep resetting to default and I’ve checked the main component multiple times, it was working perfectly last week…

 

 


Kaarel
  • New Member
  • January 13, 2026

Hello, I’m experiencing this in all my projects. While the button prototypes work as expected in the library file itself, the interactive components revert to default state while pressed in project file. It seems that on pressed state defined property overrides on the component are not respected/carried over to this state.


Laura Fegan
  • New Member
  • January 13, 2026

We are also experiencing this issue with our components


driftingsteps
  • Author
  • New Participant
  • January 14, 2026

Did this issue persist on Incognito/Private browser window?

@Todd_Coleman ​@Lucy_Hill ​@Alexandra Vega ​@Kaarel ​@Laura Fegan 


Alexandra Vega
  • New Participant
  • January 14, 2026

No, on the Incognito window doesn't happen. Only in Chrome regular window when I'm logged in.


Laura Fegan
  • New Member
  • January 14, 2026

No, it doesn’t persist on incognito. It also seems to be occurring just with nested components for us.


Lucy_Hill
  • New Participant
  • January 14, 2026

 

Did this issue persist on Incognito/Private browser window?

@Todd_Coleman ​@Lucy_Hill ​@Alexandra Vega ​@Kaarel ​@Laura Fegan 

Yes, on both incognito window and also on the desktop app.

 


Camilo T.
  • New Member
  • January 14, 2026

+1


Kaarel
  • New Member
  • January 15, 2026

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


Celine_
Figmate
  • Community Support
  • January 15, 2026

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:

  1. Go to the Support Hub
  2. Type your question
  3. 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
  • January 15, 2026

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
  • January 19, 2026

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
  • January 19, 2026

I’m experiencing this exact issue.


Nwafor Charles

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


Celine_
Figmate
  • Community Support
  • Answer
  • January 20, 2026

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
  • January 20, 2026

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
  • January 20, 2026

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

 


Celine_
Figmate
  • Community Support
  • January 21, 2026

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


M Walther
  • New Member
  • January 23, 2026

Hello ​@Celine_ 

I am dealing with a similar problem. Problem with instance properties synchronisation (variant, boolean, text) across files

It would be very helpful if you and the figma support could assist me in resolving the issue.


Celine_
Figmate
  • Community Support
  • January 23, 2026

Hey ​@M Walther , thanks for flagging this! I’ve replied to your DM with some important details on the next steps for the investigation. Please check it when you have a moment.