This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Search 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.

Learn More

Ova tema je arhivirana. Pitajte drugo pitanje ako vam je potrebna pomoć.

Firefox 16.0.1 warns on closing multiple tabs but options set not to warn

NeilFKMcLachlan
NeilFKMcLachlan
more options

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.

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.

Izabrano rješenje

Here just do this and you will be perfectly fine... even if option is selected the about:config is always set to "true" by default (on new firefox version)

Pročitajte ovaj odgovor sa objašnjenjem 👍 15

All Replies (1)

StanislavShevchenko
StanislavShevchenko
more options

For all who is interested, there is a bug report on this issue at the Firefox developer's bug tracker:

https://bugzilla.mozilla.org/show_bug.cgi?id=801072

But it got no attention so far.

  1. 1
  2. 2