Shortcuts confict on Chrome after clicking anywhere on the sidebar

What helped in my case was that I right-clicked on the element in the layer tree (context menu) before executing the shortcut. After closing the context menu, the shortcut worked.
Very annoying workaround but at least you are not blocked and can execute the desired function.

I think Figma has a problem with losing the focus state on selected/active elements and the focus then changes to the browser window.

Same thing. Latest Chrome.
The problem is that Figma loses focus in the layers area, Then a strange behavior occurs when on some selected layers the shortcuts would work and other selected layers no shortcuts would work.

the trick of right-clicking on that layer before executing the shortcut does work, but that’s no solution.

If you don’t want to deal with this and just need something that works, choose another browser like Vivaldi/Edge (also chromium)

Hey everyone, thank you again for flagging this with me!

I am passing all this information along to the team to investigate. I will give you an update as soon as I get more information on this.

Please do try the workarounds community members are suggesting and of course if this issue is disrupting your work please work with a different browser (Safari, Microsoft Edge and Firefox) or our desktop app in the meantime.

Appreciate for your patience in the meantime!

Sonoma 14.6.1 (23G93) with newest Chrome 127.0.6533.120

Shortcuts work until i undo something, then i again must click a layer or into the app for it to accept my shortucts

Thank you @eazyalf for sharing this with me, I’ve passed this along to the teams.

These problem happens in all browsers

Hey @Wrik_Sen, thanks for reaching out! What is the model of your PC and your OS?

[I see you removed the comment regarding a fix, posting this nevertheless. Maybe it helps]

It seems the bug is partially fixed for me now. In a multi-page Figma document, the bug is gone on some pages, but it’s still present on other pages.

I can’t see a pattern, it might be related to the amount of elements on the page (very full pages still have the problem, newly created don’t).

For example, I create a new page, the bug is gone. I paste the contents of another very full page into the newly created page, the bug is there again.

Chrome and system restarted. Chrome up to date. Problem still occurs.

Hey @Peter_Muller, yes apologies I had to delete my post after seeing that this is still ongoing as we can still reproduce this issue on our end.

Thanks for sharing this with me, I’ll pass this along to the team.

I will give an update once they’ve pushed a fix. Appreciate your patience in the meantime!