. (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. ⭐

[mohdkhatab]

Your own diagnostics already rule out the usual causes, and they point to a specific conclusion: this is not an extension, focus, or keyboard problem — GitHub's shortcut handler is simply not acting on the event.

You proved all three things that would normally explain a dead shortcut:

• The event reaches the page with the correct key and code (. / Period), it is trusted, and it is not default-prevented.
• The target is a plain DIV, not an input, so GitHub is not correctly ignoring the keypress because you are typing somewhere.
• Incognito mode gives the same result, so no extension is intercepting it.
• Manually changing github.com to github.dev works, so the editor itself and your access to the repository are fine.

That leaves the handler registration itself. Two things are worth testing before reporting it as a bug, because they change where the handler is mounted:

1. Try the repository root page, not a file page. Your reproduction step says "navigate to any file in repository page", which is ambiguous. The . shortcut is registered on the repository's main (Code) page. If you are on a blob/file view, a pull request page, or an issue page, the handler may not be mounted at all. Go to exactly https://github.com/<owner>/<repo>, click a neutral area, and press . there.

2. Try a different browser. You are on Chromium 156 on Windows 11. If the shortcut works in Firefox or Edge on the same repository root page, the issue is specific to how GitHub's handler interacts with that Chromium build; if it fails everywhere, it is account- or repository-independent and almost certainly a GitHub-side bug.

Workarounds that do not depend on the shortcut: use the green Code button and choose the github.dev / VS Code option, or edit the URL manually as you already discovered (replace github.com with github.dev). You can also press Ctrl+K (or Cmd+K) for GitHub's command palette and search for the editor option from there.

If the shortcut also fails on the repository root page in a second browser, report it to GitHub Support with exactly the reproduction you gave here — especially the DevTools output showing a trusted, non-prevented Period keydown on a DIV target with no navigation. That log is strong evidence that the page received the event and its handler did not fire, which is what Support needs to reproduce a client-side shortcut bug. Include your Chromium version, Windows version, and the fact that the Accessibility "Character keys" setting is enabled, as you already noted.

[queenofcorgis]

@mohdkhatab

Please note: we’ve clarified our stance on using generative AI tools like ChatGPT within our Community via this announcement. Please review the guidelines to ensure your post meets them as failure to adhere to those rules can result in action taken by our moderator team. 

You can read our updated Code of Conduct and the announcement for more details.

Please feel encouraged to continue engaging in Discussions as your authentic self though. We appreciate you being a part of the Community 🌟

[queenofcorgis]

Thank you for reporting this @noideaforeal ❤️ I passed it along to our team. If and when we have an update, I'll post back here!