In the Figma app, when we use the new feature of pan on right-click while a plugin is opened, it stops working until we switch tabs or right-click on the canvas. I don’t know if it is counted as a bug, but it should be fixed asap!
1 Like
Hi @Hasnaat - is it all plugins you use when you encounter this? Or is it only specific ones?
Asking because plugins are 3rd party developed, so if they haven’t been updated recently, it’s possible they’re not compatible with the newer versions of Figma.
If you can provide a screen recording of you running a few plugins and seeing this, please drop that here so we can review and investigate.
Yup, I’m having this issue when running every plugin, I have a screen recording but when uploading it says “New user cannot upload attachments!”
Try uploading now – you should be able to.
In the meantime, can you give me some other info?
Are you using the Figma desktop app, or using Figma in a web browser?
Are you on mac or windows?
Does this happen across both the web and desktop app?
OMG thank you so much for uncovering why my plugins would mysteriously become unresponsive unless I reopened them. It was driving me mad. I can confirm that my plugins become unresponsive on Desktop Beta UI3 after using right click to pan. They respond to clicks once again after I right click anywhere on the canvas.
1 Like
Encountering this same bug. Very easy to solve (right click anywhere, even if the plugin is already open), but not exactly the best UX…
Hopefully there’s a fix coming!
1 Like
Yup, I figured it out but couldn’t find time to tell here🙂
This can easily be resolved by right-clicking in the canvas while the plugin is opened!
But this isn’t the best UX Practice🙂
Can confirm I am experiencing the same issue. Mouse events work on the plugin initially, but after certain items are selected, the plugin stops responding to mouse events.
Hasnaat’s workaround only works for me if I right click and bring up the context menu, then, while the menu is still open, click on the plugin window.
This occurred on my mac, but the issue was fixed on that machine by clearing the cache. I tried the same on my windows laptop, but it didn’t fix the issue.
1 Like
@Eli_Crow @Hasnaat Thanks for the new context – I’ll get a bug ticket filed for this. It’s interesting that clearing the cache seems to fix on max, but not PC 
I’ll do my best to drop an update when I hear more – feel free to drop any other observations you notice in the meantime!
2 Likes
To update everyone in this thread: while I don’t have an exact window I can provide for a fix, I did file a bug ticket for this, and it was assigned to the appropriate engineering team to look at.
I’ll do my best to get an update posted here when I’ve gotten an update.
2 Likes