3 ms·

You can also tell Firefox to ignore it completely: browser.quitShortcut.disabled As well as to warn: browser.warnOnQuit browser.warnOnQuitShortcu

by sevg 11mo ago

You can also tell Firefox to ignore it completely: browser.quitShortcut.disabled As well as to warn: browser.warnOnQuit browser.warnOnQuitShortcut Well, apparently I once was aware of these because I have it set in my custom user.js. But I guess ctrl-q will always be lock screen for me, old habits die hard.

marcosdumay 11mo ago
> browser.quitShortcut.disabled The setting is there, it's editable, but Firefox seems to completely ignore it on Linux. At least up to 145.0.1.
- PaulDavisThe1st 11mo ago
  I use 144.0.2 on Linux and it works entirely fine here.
- sevg 11mo ago
  Hmm, maybe it’s still necessary to rebind ctrl-q in some cases. This says gnome has ctrl-q to quit applications: https://wiki.gnome.org/Design/OS/KeyboardShortcuts https://wiki.gnome.org/Design/OS/KeyboardShortcuts I don’t know if the above is still the default, but I have this in my gnome setup scripts anyway: gsettings set org.gnome.settings-daemon.plugins.media-keys screensaver “[‘<Control>q’]” (IIRC it’s a terminal command because trying to bind ctrl-q in Settings will quit the Settings window. And you can’t unbind ctrl-q completely, so you have to bind it to something else. You could maybe add it as a custom launcher that just runs /bin/true.)