The discussion highlights the need for an administrative or user-level setting to disable Discourse’s default keyboard shortcuts, which currently conflict with tools like the Vimium extension, speech input, and screen readers. opcourdis notes that the necessary building blocks already exist in the plugin API via disableDefaultKeyboardShortcuts and suggests implementing this as a configurable setting. satonotdead agrees, emphasizing that while many users rely on default shortcuts, others prefer custom configurations. They argue that a dedicated switch is necessary to avoid relying on alternative workarounds and reference a related topic for further context.
Hi,
Presently there is no admin setting to disable those and they may conflict in several cases :vimium keyboard shortcuts extension on firefox, speech input, screen readers, etc.
The building block already exists: the plugin API has disableDefaultKeyboardShortcuts (in
services/keyboard-shortcuts.js).
This could be either an admin setting a a per user setting in their profile.
I agree. I know that most Meta users use the default shortcuts, but others choice the shortcuts we explicitly enable and select based on our own criteria.
This has been mentioned in other topics; I left my vote because I understand that a switch is necessary so we don’t have to disable the shortcuts from alternative workarounds.
Also, I posted something that might interest you. I hope it helps.