Søg i Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Læs mere

Default keyboard shortcuts, most notably Ctrl-W

  • 3 svar
  • 0 har dette problem
  • 1 visning
  • Seneste svar af cor-el

more options

Please provide a native way to change the behaviour of Ctrl-W. I tend to switch between aZerty and qWerty keyboard layouts, as a result I sometimes hit ctrl-W when I would like to ctrl-Z some change. As a result I tend to lose some work when the tab I'm working in closes. It would be nice to be able to rebind some of the default key combinations, or at least disable them.

I found a method description that edits the omni.ja file, but also that this method is unsupported. Moreover, running ubuntu kind of rules this out as an option, as canonical has ruled that firefox is to be installed via snap, in a read-only data store.

Please provide a native way to change the behaviour of Ctrl-W. I tend to switch between aZerty and qWerty keyboard layouts, as a result I sometimes hit ctrl-W when I would like to ctrl-Z some change. As a result I tend to lose some work when the tab I'm working in closes. It would be nice to be able to rebind some of the default key combinations, or at least disable them. I found a method description that edits the omni.ja file, but also that this method is unsupported. Moreover, running ubuntu kind of rules this out as an option, as canonical has ruled that firefox is to be installed via snap, in a read-only data store.

Alle svar (3)

more options

You can disable "Ctrl+W" via the autoconfig.cfg file.

See:

more options

Thank you for your reply, I had already found this.

Quoted from your second link:

"To use Autoconfig, place two files into the Firefox installation directory." " on Windows and Linux, they go into the same directory where Firefox is installed"

As my firefox installation is on a read-only filesystem, this solution cannot work for me. The location of this file is hard-coded, I would say rightfully so, therefore this is a dead-end for me.

Could someone provide a rationale for not making hotkeys configurable natively, from the ui? I believe this has been requested repeatedly over the years.

Thanks.

more options

You can consider Firefox from the official Mozilla server if you currently use the Flatpak/Snap version with limitations or a version from the repositories of your Linux distro.