Open Bug 1267145 Opened 9 years ago Updated 3 years ago

Add ability to disable keyboard shortcuts of Firefox itself

Categories

(Firefox :: Keyboard Navigation, defect)

Product:
Firefox
Component:
Keyboard Navigation
Type:
defect

Tracking

()

Tracking Flags:
Tracking Status
firefox48 --- affected

People

(Reporter: yuki, Unassigned)

References

(Blocks 1 open bug)

Details

In enterprise use, needless (dangerous) keyboard shortcuts are needed to be disabled. For example, one of my customer hope to disable Ctrl(Command)-P to prevent any printing. Thus I use some addons to disable keyboard shortcuts of Firefox itself: * https://addons.mozilla.org/firefox/addon/key-config/ * https://addons.mozilla.org/firefox/addon/ui-text-overrider/ Actually I use UI Text Overrider for 90000+ client PCs of my customers. https://docs.google.com/spreadsheets/d/1gn8fFl4iseOqLEz_UIEbHCEZ7R01VW2eDlxJaFRNKEo/edit#gid=624184169 However, these addons are XUL-based and XUL will be deprecated in near future. Then there are two choices: A) Add new WebExtensions API to disable Firefox's built-in keyboard shortcuts. B) Add some secret preferences or something to disable Firefox's built-in keyboard shortcuts. The choice A seems too dangerous and less useful for most type addons. So the choice B looks good for me.
The bug 1215061 seems about features to define new keyboard shortcuts. On the other hand, this aims to disable built-in (and if possible, including provided by addons) keyboard shortcuts.
Option A is bug 1325692.
See Also: → 1325692
I lost my progress on a webpage again because I mistakenly pressed Ctrl-w (trying to delete a word). I'd like to disable all these destructive Ctrl-w, Ctrl-q shortcuts, and the annoying Ctrl-p. I prefer to do them using my mouse.
As browser-based editing becomes more common, advanced text-navigation becomes more important. I use Jupyter Notebooks (and Lab) a lot at work, and would like to use certain keybindings for code navigation (Emacs in my case). Ctrl-N, Ctrl-B and others make this impossible. Giving the option to change or at least disable them would be greatly appreciated!
Severity: normal → S3

The severity field for this bug is relatively low, S3. However, the bug has 11 votes.
:dao, could you consider increasing the bug severity?

For more information, please visit auto_nag documentation.

Flags: needinfo?(dao+bmo)

The last needinfo from me was triggered in error by recent activity on the bug. I'm clearing the needinfo since this is a very old bug and I don't know if it's still relevant.

Flags: needinfo?(dao+bmo)

(In reply to Release mgmt bot (nomail) [:suhaib / :marco/ :calixte] from comment #6)

(...) this is a very old bug and I don't know if it's still relevant.

It's still not possible to edit and/or disable shortcut (see also #972662, #1635774), so I'd say it is still relevant

I would just like to point out that not being able to disable keyboard shortcuts in Firefox' Kiosk mode makes this mode completely useless. What's the point of a kiosk point if user can press CTRL+T, CTRL+N, CTRL+J, CTRL+Q (well, this can be avoided by doing a shell script like firefox ... && exec "$0" "$@"), CTRL+W, etc?? Thanks

You need to log in before you can comment on or make changes to this bug.