. (dot) keyboard shortcut to open vscode does nothing

[noideaforeal]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Codespaces

Body

Description

The . keyboard shortcut to open vscode does nothing on repo pages. The key event fires correctly (verified via DevTools) but no navigation or editor launch occurs. Manually changing github.com → github.dev in the address bar works fine, so the editor itself is functional.

Reproduction Steps

1. Log in to github.com
2. Navigate to any file in repository page
3. Click on a neutral area of the page
4. Press the . (Period) key

Logs

DevTools console listener output on keydown:

key: . code: Period target: DIV
defaultPrevented: false
isTrusted: true

The event reaches the page with correct key/code, is trusted, is not default-prevented, and the target is a plain DIV (not an input). GitHub's handler is simply not acting on it.

Environment

Browser: Chromium 156.1.98.63
OS: Windows 11 26H2
GitHub Accessibility setting "Character keys": sign in - enabled
Extensions: tested in incognito — same result, so not extension-related.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐