Option to disable command keys

[jsoref]

Select Topic Area

Product Feedback

Body

I'm doing historical archaeology and the cmd-f trap is annoying me. It's nice that I can turn off . so that I don't accidentally end up in github.dev, but, I'd really like to have the option of GitHub not stealing my browser's navigation strokes.

[cehfisher]

Hi @jsoref - I wanted to follow up on this stale issue. Have the recent keyboard changes resolved this issue for you? If yes, could you please close the issue? If no, what additional changes are needed? Please supply detailed instructions to reproduce your issue and include screenshots and/or URLs, if applicable. Thank you! (cc @queenofcorgis)

[jsoref]

Do you have a link to an announcement for the "recent changes"?

[cehfisher]

Hi @jsoref there are a number of GitHub blog articles on the topic of keyboard commands and accessibility support. Since your original issue was created over a year ago, I wanted to be sure you are still encountering the same experience. Thanks!

[jsoref]

I've had a concussion and can't engage as much as I used to, here's a few things that trip me up all the time:

There's a setting (which I was referencing when I said that I can turn off .):

Character keys

Enable GitHub shortcuts that don't use modifier keys in their activation. For example, the g n shortcut to navigate notifications, or question mark ? to view context relevant shortcuts. Learn more about character key shortcuts.

---

It appears to apply to the repository tree view, but it doesn't apply to the source code view, so, pressing . does nothing when browsing https://github.com/check-spelling/check-spelling/, but pressing . opens https://github.dev when browsing https://github.com/check-spelling/check-spelling/blob/main/README.md

This is not particularly intuitive from https://docs.github.com/en/get-started/accessibility/keyboard-shortcuts#about-keyboard-shortcuts

There's also this thing:

But, it too doesn't work in file views. I have a hard time squaring the claims from the user interface or documentation with my experiences.

---

Otoh, Some don't work as documented (and probably haven't worked for forever):
https://docs.github.com/en/get-started/accessibility/keyboard-shortcuts#source-code-editing

Keyboard shortcut	Description
Command+Y (Mac) ...	Redo

That doesn't work, because browsers have reserved cmd-y for history for a long time:

https://support.google.com/chrome/answer/157179?hl=en&co=GENIE.Platform%3DDesktop#zippy=%2Ctab-window-shortcuts%2Cgoogle-chrome-feature-shortcuts

Google Chrome feature shortcuts

Action	Shortcut
Open the History page in a new tab	⌘ + y

---

That said, I'm suffering from a concussion 🤕 and do not feel that it would be productive to have a discussion about issues, so if people are unwilling to be charitable to my issues, I'd rather close them than have someone ask questions instead of spending time chartiably looking at them.

Please indicate your preference and I'll close any issues that disturb your sensibilities.

[cehfisher]

Hi @jsoref - so sorry to hear about your concussion. We only asked for additional details as we could not replicate the issue on the pages/features we tested, but didn't want to close the issue if you had more info you could share. We will file this with our Accessibility team so that it can be reviewed and will follow-up here with any additional questions or updates. Thanks again and get well soon!

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