Ctrl+G and other shortcuts are misconfigured and conflict with Firefox on Linux

[foresto]

Select Topic Area

Bug

Body

Github's "jump to line" keyboard shortcut conflicts with the find-next shortcut in my browser (Firefox Linux): Control+G.

This is apparently a bug, as Github's shortcut help page says it's supposed to be Alt+G.

I cannot describe how maddening it is to have a web site hijack my browser navigation controls, especially those that I use frequently. Adding further injury to insult, there appears to be no way to disable or reconfigure it.

---

Edit, because I don't feel like writing up a separate report right now:

Alt+S is also being intercepted by GitHub, preventing me from opening my browser's history menu.

This is bloody ridiculous.

[KongSugoi]

I think you can try to change shortcut in your linux

[foresto]

I think you can try to change shortcut in your linux

No, it is a standard browser shortcut. Even if I could, I wouldn't change standard shortcuts to accommodate Github hijacking them.

[cehfisher]

Hi @foresto - thank you for providing this feedback! We wanted to follow up on this reported bug. Is this still an issue you can replicate? If it is resolved, could you please close out this issue? If it is not resolved, we will file this as an issue for the Accessibility team to review. Thank you! (cc @queenofcorgis)

[foresto]

Hi, @cehfisher .

Control+G seems to be working now, but Alt+S and various other browser shortcuts (reported in #113472) remain broken and/or hijacked on pages that display code.

Please do file the issue with the Accessibility team. Thank you.

[cehfisher]

Hello @foresto would it make sense to close this issue since the original issue has been resolved and shift this focus to looking at #113472?

[foresto]

I am reluctant to close this before the underlying problem has been resolved.

While there is another community discussions forum post concerning the remaining symptoms, that post is more of a parallel feature request, is not in a bug tracker, and has not been acknowledged by GitHub. I fear that closing this one would make it even easier for the still-active problem to be lost, forgotten, swept under the rug, or otherwise ignored.

Given that it has taken a year for anyone at GitHub to respond here at all, and that GitHub (strangely) seems not to accept bug reports against GitHub itself, I think that fear is well founded.

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

[github-actions[bot]]

🕒 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 out of date at the bottom of the page.

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 Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[foresto]

This is a despicable practice.

[foresto]

Suggestion:

Instead of automatically down-ranking unfixed bug reports, how about automatically reminding the developers to fix the bugs, or automatically reminding the managers to allocate time for it?