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.