Firefox just updated itself to version 16.0.1. Now, when attempting to close multiple tabs, I get the "Confirm close" warning even though the "Warn me when closing multiple tabs" option is unchecked. I tried checking that option, confirming the change, then unchecking that option again & confirming the 2nd change, too. This has made no difference. Firefox is not obeying the option setting.
The problem didn't occur before the update to 16.0.1 but did occur in the first session afterwards & has persisted since.
Solved! Go to Solution.
hello NeilFKMcLachlan, unfortunately it isn't possible to deactivate the warning which shows up when you select "close other tabs" at the moment due to a side effect by another bug fix. in firefox 18 there will be a preference added in about:config (browser.tabs.warnOnCloseOtherTabs) which makes it possible to hide the warning again, see bug #772319.
To madperson: Please note that my remarks are directed at Mozilla, not you.
That simply isn't good enough. The warning is a nuisance that I'd got rid of by setting an option. Now some twerp has decided I'm too stupid to be allowed to do that. The explanation of why & the advice to wait until version 18 for a fix both simply add insult to injury.
In the Options dialog, you ask me if I want a warning when I close multiple tabs. I've said "No". What part of "no" don't you understand?
The more I encounter this piece of stupidity, the more annoying it gets. The assumption that no user knows what he/she is doing is one of the things that made Windows Vista such a disaster. Firefox shouldn't be copying failure. If Mozilla had time to cause this problem in version 16, it has no excuse for waiting until version 18 to undo the damage. It has time to reverse the change now.
There's a good argument for the warning option to be enabled by default. There's none whatever for making it compulsorily enabled, regardless of the user's wishes.
It is, of course, possible that someone will go into the options dialog, disable the warning option & then close multiple tabs by mistake. In that situation, it's the user's own fault. If it's too much trouble to undo the error, the user can re-enable the warning option & stop it happening again.
If there's unsaved data on one of the pages, that page ought to (& most will) warn the user that closing/leaving the page will lose the data. If there's no warning, it's the fault of the page code -- provided, of course, that the browser raises the relevant event when the tab is about to be closed. If the browser isn't raising that event for some reason (e.g., because the tab with the page isn't the active tab), that is the problem requiring attention.
Yup, the same thing happened to me. I've checked the options page, checked and rechecked the no warning option and it didn't work. Also checked config as well and the option for browser.tabs.warnOnClose = false as it should be.
Unfortunately, the option/config are doing nothing. This needs to be rectified.
I've been pulling my hair out on this. It brought me to the support forum for the first time. I absolutely hate "Nag" screens and prompts that I have to click through to confirm that I want the product to do exactly what I asked it to do. If I can't get rid of them, I'll try another product. I'll be patient, but really, wait for the next full release?
Hallo Firefox its been a week already, Firefox come out and play.......Firefox come out and play........Firefox come out and play.......version 18? No that’s not an answer sorry!
Or maybe you could make a popup saying “We will now update your browser to a crappy version with annoying popups and perhaps general malfunction in your browsing experience” Many regards the hard smoking cigar team at Firefox!
I just patched my Firefox to disallow this annoying behaviour. On OS X, unfortunately, but the patch should be similar on Windows, although the paths will differ. Used Midnight Commander to edit inside omni.ja, which is a plain Zip archive.
Thanks, unicodefreak. I might do the same. However, it doesn't realy solve the problem. An update to Firefox is liable to overwrite the patched file & bring the unwanted nagging back, in which case the patch would need to be repeated. That could happen many times & I don't like having to apply the same fix multiple times.
Also, from what I can see, this fix still commits the mistake of ignoring the setting of the "Warn me when closing multiple tabs" option. If I decide that I want the warning -- temporarily, for an inexperience user, say -- I'd need not only to set the option but also to reverse the code patch.
Furthermore, this is a problem created by Mozilla & ought to be fixed by Mozilla. They need to know they've got it wrong. They need to know that "Wait a couple of versions" isn't good enough. Anyone who actually wanted the warning message could have had it, just by setting the option. The sole effect of their change is to impose the warning on users who don't want it. It doesn't in any way help those users who do want it. Mozilla ought to have known better. Since it seems they didn't know better, we need to get the message across to them so that they will know better in future.
It is probably worth noting that the bug fix is now included in Firefox
beta Aurora, so some of you may consider changing channel and flipping the pref browser.tabs.warnOnCloseOtherTabs
I think it is realised that the changes are contentious, & whilst I am not attempting to censor discussion I feel I should point out that this is not the best place for such a conversation.
(2nd edit minor typos -J99)