Dealing with browser shortcut conflict in codespaces

[sheldonhull]

Select Topic Area

Question

Body

Is there a documented approach to ensure I can continue to use normal application shortcuts like cmd+w to close a tab, but not have it closing a chrome tab? I can remap my keys in all areas I guess, but wanted to try and avoid retraining muscle memory.

Examples:

Cmd+w close a tab, but chrome takes this as a close the chrome tab instead.
Cmd+q quit would quit all chrome instances up.

If there's a simple way to ensure the codespace opened treats it as an application I'd like to know so I can avoid dealing with remapping just for browser based codespace.

[djbrown]

I would really love to see a fix/workaround in the browser. Docs say:

For several issues (especially keybindings or those listed with a workaround for the desktop), you can install and use a Codespace as a progressive web application (PWA).

[sheldonhull]

Did you try this and it fix it? That's an acceptable answer imo without a special extension or this I'm guessing those browser mappings can't be overridden.

[djbrown]

I now wanted to try the PWA workaround, but seems like it's not available for Firefox.

[djbrown]

see also microsoft/vscode#83343 (comment) ("master issue"), microsoft/vscode#108217 and microsoft/vscode#197731