Using shortcuts inside browser

Description

Some VSC shortcuts do not work because they are reserved for browser-specific actions. For instance, Strg + N usually opens a new file in VSC, but is reserved by various browsers for creating a new tab or window.

Do you have a plan for improving this? Of course every shortcut is accessible by the command palette, and commands which are unaccessible by the default shortcuts can be reconfigured to be accessible by other shortcuts, but this would require everyone who wants to give code-server a try to configure his instance first before being able to use it productively, and having powerful editing capabilities without the need for extensive configuration is one of VS Code’s key features.

Related Issues

[hbjydev]

Not strictly true. There is a way to do it, but it’s kind of a local-app hybrid. If you’re on Chrome (sorry Firefox users!) you can go to Menu > More Tools > Create Shortcut… and just tick “Open As Window” when you make it. Then, just use that to work with Coder and all your <kbd>ctrl+?</kbd> shortcuts will work. It is a browser restriction, although there is a code-side workaround to that too. When you listen for each event, you can put event.preventDefault();. That’ll stop any default handling from occurring, including the browser trying to process the keybinds iirc.

[nhooyr]

I think most users just aren’t aware of the PWA and how it works.

Opened https://github.com/cdr/code-server/issues/1726

And we should show a popup #1599