Much appreciated! Figures that it was a 21-year-old bug. I'm wondering why it took so long, but regardless, you're my savior.

Coincidentally, when Mozilla's blog post about shipping a big cookie separation feature was on the front page recently, the first thing I thought was "but when will they let you disable CTRL+Q? It'd be so much easier to do than this." In the age of Chromium, issues like this will lead to death by a thousand cuts for Firefox. The cost of switching is marginal for most people, as Chrome has become too well-architected as a browser which ends up connecting you to Google. I myself was almost tempted to switch because of this and other relatively minor issues that ended up snowballing together, and I'm a person that makes a deliberate effort to like Firefox. I have to wonder why nothing changed in 2002, when so many people were making so much noise about this.

Whoa, that is incredible, thank you SO MUCH! <3

I don't think I can explain the extent to which this simple papercut has been vicious and painful to me.

So many times, I've started writing some long post in a text field and accidentally lost it due to pressing some wrong keyboard shortcut (oops, you pressed backspace outside a text field! oops, we bound this key to 'reload the page', oops you closed the form by pressing ESC!). It's always a particular type of sinking feeling to have to start writing all over again.

Now there are extensions for this, and some of them even work. But what's my natural instinct when I have data in a text field I really don't want to lose because I would feel terrible losing it?

Well, ^A ^C and go paste it in a notepad, maybe even finish editing it there.

... and then Firefox quits, maybe because my layout switched between AZERTY and QWERTY by accident, maybe because my finger slipped between A and Q. And I get to stare at my desktop, crushed and defeated, having lost my data at the exact worst possible time...

I was seriously starting to consider maintaining my own Firefox fork, and I _cannot thank you enough_!

Fixing the Ctrl+Q issue is great, but I still think extensions such as Form History Control are essential for all other situations. I'd very much appreciate if Mozilla could vet it for security; I'm always afraid of some developer selling out or being hacked and a future update introducing a backdoor.

> So many times, I've started writing some long post in a text field and accidentally lost it due to pressing some wrong keyboard shortcut (oops, you pressed backspace outside a text field! oops, we bound this key to 'reload the page', oops you closed the form by pressing ESC!).

For me it's often ctrl+w to delete one word, which terminals have gotten me used to. I don't want the shortcut removed because I use it all the time to close tabs outside a text box, but it also still working while focused in one is annoying.

Oh god yes, backspace outside the text box is the worst. Some websites mitigate this themselves, but it would really be nice if the browser could take care of this.

Firefox already lets you disable that using the browser.backspace_action setting in about:config: https://support.mozilla.org/en-US/questions/924490

I can't find any words to tell you how thankful I am!

My FF is configured to delete all history upon exit, so I have lost SO MANY interesting browsing sessions over the years due to CTRL+Q!

Thank you very much for finally resolving this!

Not a bug I personally was very affected by, but:

Thank you so much fpr actually fixing bugs!

If my impression of Mozilla is correct you must have both done the work and possibly also fought hard to be allowed to merge it.

(Now, if any Mozillan feel inspired I'd love to get my real extensions back, particularly TST without top tab bar and also Scrapbook.)

Awesome, thank you. This will fix most of my accidental firefox closing. Too bad that I sometimes fatfinger ctrl-w as ctrl-shift-w.

oh wow!! that's amazing, i've been waiting for this one forever.