Join us and the lead editor of IRL, Mozilla's multi-award-winning podcast, for a behind-the-scenes look at the pod and to contribute your ideas for the next season, themed: "AI and ME." Mark your calendar and join our Community Call on Wednesday, Aug 7, 17:00–17:45 UTC. See you there!

Avatar for Username

Mozilla サポートの検索

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.

詳しく学ぶ

このスレッドはアーカイブに保管されました。 必要であれば新たに質問してください。

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

  • 21 件の返信
  • 76 人がこの問題に困っています
  • 1 回表示
  • 最後の返信者: StanislavShevchenko

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.

選ばれた解決策

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)

この回答をすべて読む 👍 15

すべての返信 (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