-
Notifications
You must be signed in to change notification settings - Fork 154
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Typing anywhere results in triggering shortcuts (comments, layer names, etc...) #63
Comments
Hi. Can you make this case on video or gif? |
This happens to me as well. Whenever I create a style and name it words including an "N", it triggers the "Find Next Frame - N" shortcut. I am using Linux Mint 19.2. As a temporary fix I am back on v0.5.4 as problem still occurs on v0.5.5 |
I have the same problem. |
I can confirm the issue, Figma desktop 0.5.6 on Ubuntu 19.04 |
Cases is a frame. The issue seems to occur to me regardless of component hierarchy. In fact, it occurs in both menus and text components. I can consistently reproduce by typing "i" which triggers the "Pick color" tool. I also get issues if i type "+" or "-" which triggers zoom. "shift+R" triggers the rulers, "shift+2" triggers zoom to selection. I can trigger the next frame shortcut as mentioned by @kylebriffa7 however this one only occurs if I'm editing something in the menus and not for editing text components inside the design. |
You can disable the main menu in the app settings. Without it shortcuts should not double trigger |
I can confirm this solves all my issues. Thank you 😄 |
I see that you have a commit that will close this, but I'll report my problem just in case it isn't caught by that. The color inspector opens when I'm typing out a comment and press "i". Looking forward to this being fixed! |
Bug description
Typing anywhere wrongly triggers shortcuts. This includes typing to rename a layer, enter values or post comments. This behavior is only seen in the linux app and not in the web app (or windows/mac app, which means it is linux specific)
The text was updated successfully, but these errors were encountered: