We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Tìm kiếm hỗ trợ

Tránh các lừa đảo về hỗ trợ. Chúng tôi sẽ không bao giờ yêu cầu bạn gọi hoặc nhắn tin đến số điện thoại hoặc chia sẻ thông tin cá nhân. Vui lòng báo cáo hoạt động đáng ngờ bằng cách sử dụng tùy chọn "Báo cáo lạm dụng".

Tìm hiểu thêm

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

  • 21 trả lời
  • 76 gặp vấn đề này
  • 1 lượt xem
  • Trả lời mới nhất được viết bởi StanislavShevchenko

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.

Giải pháp được chọn

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)

Đọc câu trả lời này trong ngữ cảnh 👍 15

Tất cả các câu trả lời (1)

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