Component variant properties break every time — reproducible bug on double-click rename

Hi ​@Caroline Matter 👋 Thanks for the detailed write-up and the clear repro steps — that really helps.

I tried to reproduce this on a fresh 2-variant component set and wasn't able to trigger the break. Here's exactly what I did:

• Created two components and combined them as variants (single Type property, values Regular and Hover)
• Double-clicked the "Hover" variant's layer name in the left panel — the edit field correctly showed the full Type=Hover string, fully selected
• Committed with Enter, then double-clicked the same layer a second time to edit again
• The property mapping held — no "invalid name" error and the Type dropdown stayed intact
• Quick gif of my test 👇

A few questions:

• When you double-click a variant the second time, what does the edit field pre-populate with — the full Type=Regular, State=Default string, or already just Regular, Default before you type anything?
• Are you editing the name in the left layers panel, or somewhere else (right panel, rename dialog)?
• How are you committing the edit — Enter, Tab, or clicking away?
• Does this happen on a brand-new file with a freshly created 2-variant set, or only in this specific library?
• Are you on the desktop app or browser, and which OS? Any non-English keyboard/IME active?

If you can share a short full-screen screen recording of the second double-click, that would likely be very helpful.

Thanks for the additional info! — Jaycee

​@Caroline Matter same issue for me.

Hey ​@Jaycee Lewis, thank you so much for your quick reply.

I'm sharing a video of one of my Design System Library components: the Filters button (it's like this on every component). As you can see, initially everything seems normal; the properties are there and correctly assigned. It's when I go into the component's variant a second time to make changes, when I double-click the "Hover" variant's layer name in the left panel—the edit field is incorrect and shows only "Regular" and "Default" before I type anything.

My answers :

When I double-click a variant the second time, the edit field pre-is populated with just Regular, Default before I type anything

I editing the name in the left layers panel 

I only worked on Figma the desktop App, on macOS Sequoia 15.6.1 with a standard keyboard
I attached a complete video if my GIF doesn’t work well

Thank you for paying attention to my request — Caroline

​@Gabriel Marquis-Angulo I know that you have the same issue in your entire Design System Library

Hey ​@Caroline Matter 👋 I've filed this with our team to investigate – Ticket ID 2026934. Please keep an eye on your inbox for any requests or replies.

Really appreciate you taking the time to report this so thoroughly!

Jaycee

Hey ​@Caroline Matter — echoing ​@Jaycee Lewis‘s appreciation for your report. Quick update that our Engineering team is actively working on a fix. Additional updates here: Variant properties (State=Default, Color=Blue) rejected as invalid when renaming layer.

​@Jaycee Lewis  Our team have the same issue in Design System Library...😫😫😫

Hey ​@Tom Reem we’re experiencing the same issue as well. I’ve tried restarting the app, using the web version, and switching browsers, but the issue still persists.

Could you please prioritize this? It is currently disrupting our production workflow.

Thank you.

​@Celyn_L first glance seems to be working, though variant layer names now contain the entire string, even if I create a new component. No sure what impact that has other than not being convenient. 

Hi ​@mark.braithwaite, thanks for confirming that the original issue appears to be resolved, and I appreciate you calling out this behavior.

I'm checking with the team to confirm whether the variant layer names displaying the full property string is expected and I'll share an update here as soon as I hear back.

Thanks again for flagging it!

Hi ​@Celyn_L , thank you for fixing this bug so quickly. It's fixed and it's working quite well. However, I'm experiencing the same behavior and feedback as ​@mark.braithwaite. It's true that it works, but it's not very practical.