User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:36.0) Gecko/20100101 Firefox/36.0 Build ID: 2015022000 Steps to reproduce: Closed window with ctrl+q Actual results: Window closed Expected results: window should not have closed because warn on multiple tabs close is enabled in preferences

why does this bug report page look all funky all of a sudden?

Thanks for taking the time to report this! Does the problem still happen if you start Firefox in Safe Mode? (Safe Mode disables extensions and themes, hardware acceleration and some JavaScript stuff in order to exclude some possible reasons for problems. It does not disable plugins which are add-ons.) See http://support.mozilla.com/en-US/kb/Safe+Mode And does this also happen with a new and empty profile? See http://support.mozilla.com/en-US/kb/Basic%20Troubleshooting#w_8-make-a-new-profile and http://support.mozilla.org/kb/Managing%20profiles

Yes to both

Did you try with all add-ons disabled? No idea what's different about your config, hence trying to find out.

Doesn't safe mode disable all addons? It happens in safe mode.

Do you have session saving enabled ("When Firefox starts: Show my windows and tabs from the last time")? Try one of these addons: * https://addons.mozilla.org/en-US/firefox/addon/warn-before-quit/ * https://addons.mozilla.org/en-US/firefox/addon/cmd-q-catcher/ * https://addons.mozilla.org/firefox/addon/disable-ctrl-q-shortcut/

It still happens with and without session saving enabled.

User Agent Mozilla/5.0 (X11; Linux x86_64; rv:46.0) Gecko/20100101 Firefox/46.0 Build ID 20151217072309 I replicated this and I think CTRL+Q is different than closing tabs (by pressing "x"). When you press "x" to close you browser, while having multiple tabs open, a warn message appears. However when pressing CTRL+Q or File > Quit the message does not appear. I tested this on Ubuntu, Mac and Windows (Alt+F+X) and the same happens. I changed the component to Tabbed Browser. If you think this in not the right one, please fell free to change it to a more appropriate one. Is this designed to work like that?

See also bug 419009.