Dealing with browser shortcut conflict in codespaces #40566
Replies: 3 comments 2 replies
-
I would really love to see a fix/workaround in the browser. Docs say:
|
Beta Was this translation helpful? Give feedback.
-
see also microsoft/vscode#83343 (comment) ("master issue"), microsoft/vscode#108217 and microsoft/vscode#197731 |
Beta Was this translation helpful? Give feedback.
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
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.
Beta Was this translation helpful? Give feedback.
All reactions