Editor loses focus after keyboard shortcut to switch to code editor

[MatzeKitt]

Description

If I swith to the code editor via keyboard shortcut, I cannot switch right back afterwards via keyboard shortcut, since the editor loses the focus. I need to click inside the code editor to switch back to the visual editor.

If the more menu is open on the upper right corner of the editor, I can switch between both editors with keyboard shortcuts every time.

Step-by-step reproduction instructions

1. Open a post/page edit page in the backend.
2. Click into the editor to get focus.
3. Press the keyboard shortcut to switch to the code editor.
4. Press the same keyboard shortcut again.

Screenshots, screen recording, code snippet

No response

Environment info

WordPress 6.0
No Gutenberg plugin installed
Safari 15.5
macOS 12.4

Please confirm that you have searched existing issues in the repo.

Yes

Please confirm that you have tested with all plugins deactivated except Gutenberg.

No

[Mamaduka]

Probably related #40577.

[afercia]

Adding some more context from #52719 (closed as duplicate).

Actually there are two problems with this:

1. For keyboard users and assistive technology users a focus loss is a terrible experience as they are 'catapulted' back to the document root and they have to start navigating the page from scratch.
2. When a full focus loss occurs, all the Editor keyboard shortcuts don't work any longer. For example Cmd+K to open the command center doesn't do anything. See Command Center: Keyboard Focus lost when toggling Editor Preferences or Code Editor #52301

Please see #52719 for some additional considerations.

[Mamaduka]

When/if code highlighting of the currently selected block is implemented (#26738), we can use it as a new target for the focus.

At the moment, I think @afercia's suggestion from #52719 (comment) could work as a middle ground.

[Mamaduka]

It looks like the keyboard shortcut now works as expected, even after the focus is moved to the document root.

[afercia]

Just tested on trunk and can confirm @Mamaduka feedback. I think these shortcuts are now attached to a higher level of the React tree and work even when focus is on the document root.

However, when swithinc visual / code and vice-versa, the focus loss still occurs. As such, it appears first part of the problem reported on #52719 is now solved but focus still needs to be managed.