Skip to main content
Solved

[FIXED] Pressing ‘Q’ closes annotations unexpectedly

  • December 29, 2025
  • 11 replies
  • 188 views

Sofia Sagel

Whenever I create an annotation on an image, the image edit bottom floating bar appears and if I write anything on the annotation containing the letter “Q”, Figma takes it as the shortcut for “Select area” and the annotation disappears.

 

Help! I think this is a bug.

 

[Moderator note: The title of this post was updated from “How to prevent annotations from quitting when ‘Q’ is clicked” to “Pressing ‘Q’ closes annotations unexpectedly” on Jan 6, 2026.]

Best answer by djv

Hey All, thank you for your patience while I team worked on fixing this issue! 

Our team just pushed the fix. Please refresh your tabs and let us know if you run into any further issues. 

11 replies

Joesak
  • New Member
  • January 3, 2026

I experienced this bug too!


Tom Reem
Figmate
  • Figmate
  • January 5, 2026

Hey ​@Sofia Sagel and ​@Joesak — thanks for catching this!

I tested this in both the Figma Desktop App and the browser using Dev Mode in a Design file, and in my testing the annotation behavior appears to be working as expected. The image edit bar didn’t appear, and annotations did not exit when entering the letter Q.

To help narrow this down further and make sure we’re not missing an edge case, could you reply with a bit more detail on the following?

  • Does this happen for you in the browser, the Figma Desktop app, or both?
  • If you’re using the desktop app, can you confirm you’re on version 125.11.6 or later?
  • If you’re using the browser, can you confirm it meets Figma’s system requirements?
  • If possible, please share the steps leading up to the issue (e.g. any categories or properties added to these annotations) along with a short screen recording.

Appreciate you helping us dig into this. I’ll keep an eye out for your reply and pass any updates along to the appropriate team.


Joesak
  • New Member
  • January 5, 2026

Hi Tom, thanks for the response.

 

I tried it again today, and it’s working properly right now.

As for the details, yesterday I only tried in desktop app and didn’t try it on the browser.

 

Thank you!


Sofia Sagel
  • Author
  • New Member
  • January 5, 2026

Hi Tom, 

 

On my side, the issue persists, the desktop app version is the latest yes. I tried to reproduce the error on the website and it’s happening there as well.

 


zarkokuvalja
  • New Member
  • January 5, 2026

Same issue, Figma Desktop on Windows 11 25H2


AudreyVign
  • New Member
  • January 5, 2026

Same issue - desktop app (mac) 14.6.1


Tom Reem
Figmate
  • Figmate
  • January 6, 2026

Hi everyone,

Thanks so much for sharing your experiences and confirming these details. I’ve passed these reports to our product team, and they’re aware of the issue.

I don’t have a full solution or access to a timeline yet, but we’re keeping a close eye on this. We will share updates as soon as we can.

Really appreciate your patience here, and keep us posted on how it’s going.


Tom Reem
Figmate
  • Figmate
  • January 7, 2026

Update:

We were able to reproduce the issue on our end, and our engineering team is actively investigating the cause. We’ll continue to follow up here as soon as we have more details to share.

Thank you all for your patience while we work to get this back up and running as expected.


Remy_Guestereguy

Happens here on a certain scenario : 

Keyboard layout: French - AZERTY

When adding or editing an annotation on an “image” frame then, as the image is focused during annotation, Q is used as a shortcut to select the action “Select area” which cause loosing focus and closing the annotation.

Workaround : Put your image in a frame then select your frame to add the annotation


djv
Figmate
  • Community Support
  • Answer
  • January 7, 2026

Hey All, thank you for your patience while I team worked on fixing this issue! 

Our team just pushed the fix. Please refresh your tabs and let us know if you run into any further issues. 


Sofia Sagel
  • Author
  • New Member
  • January 22, 2026

Thanks! It’s fixed :))