Skip to main content

Since a recent update, it’s very cumbersome to edit component variant name since the keyboard arrows and shortcuts do not behave as expected.

When creating a new variant and clicking the variant field to update the name, the text gets selected, which is good. Previously, hitting the left-right arrows would move the cursor within this field to adjust the variant name and it would be possible to use keyboard shortcuts to move to the end/beginning or jump/select words.

Now, clicking the left-right arrows do not move the cursor within the field, but instead move the focus to the dropdown button next to the field, like the tab key would normally do. This is even more of a problem when the name is long, either needing to retype the name even if I wanted to simply adjust it (eg adding suffix/prefix) or needing to select the whole component, then open the variant panel to edit the specific long name.

The arrow keys and keyboard shortcuts do work as expected in the ‘Edit variant property’ panel.

 

Hi ​@Frederic_Giroux 

 

I understand you're experiencing an issue with editing component variant names in the right panel, specifically with the left/right arrow keys not moving the cursor as expected.

I tested this on my side in both the browser and the desktop app, and the left and right arrow keys did move the cursor within the field as expected for me.
 

 

To help us narrow this down, could you please check a few things?

  • Is this happening only in your browser, only in the desktop app, or in both?

  • If you're using the desktop app, please ensure you're on the latest version.

  • Is this issue occurring in a specific file, or are you seeing it across all your files?

  • Could you please try these quick fix to see if there's any difference?

    • Close any Figma tabs you're not using.

      • Browser: Force-quit your browser and open Figma in a new window.

      • Desktop App: Force-quit the Figma Desktop app and restart it.

 

If the issue still persists after trying these steps, I recommend submitting a support request directly to us by following this guide: Submit a bug report. This way, we can take a closer look at the issue!

Thanks,

Hi ​@Junko3 , I reloaded all my tabs this morning and I do not have the issue anymore. Thanks for taking the time to answer

Hi ​@Frederic_Giroux,
That's great news! Thanks for letting me know!

I am experiencing this same issue. Whenever I use the arrow keys in the variant name input field, it instead tabs to the adjacent buttons. I closed ALL my open Figma tabs (oof 😣), restarted the application, and the issue persists.

  • I am only seeing the issue in the desktop app (v125.6.5) in macOS (Sequoia 15.5).
  • I am experiencing the issue across multiple design files.
  • Restarting the app and then my entire machine did not resolve the issue.
  • Closing tabs did not have any impact.

Not sure what Frederic did that I’m missing. Any guidance or should I submit a bug report?

Hi ​@Patrick_Hays & ​@Junko3,
I don’t know what I did either, which is unfortunate since the issue has come back for me too.

  • I’m having the issue on the desktop app (version 125.6.5) in macOS (Sequoia 15.5)
  • The issue is not occurring when accessing Figma on Chrome
  • The issue is across multiple files
  • Restarting the computer and tabs haven’t solved the issue neither 

I experience the same in the desktop app. Re-launching the app or re-opening a file doesn’t help.

Hi, thanks for flagging this!

 

I just tested on my end and I'm seeing the same behavior in both the Figma desktop app and the Chrome browser.
It looks like this issue has resurfaced.

I’ll go ahead and share this with our team and will keep you posted if there are any updates.

 

Thanks again for your patience.

I just noticed that this bug is not occurring for me right now. Hopefully it is fixed permanently!

 

​@Junko3 Do you know if this specific issue was addressed in a recent release?

Hi there,
 

Yes, I’ve confirmed that our engineering team has shipped a fix for this issue.
If you’re no longer seeing the behavior, it’s likely that the fix addressed it.

 

Thanks again for flagging it earlier!

Terms & ConditionsCookie settings