搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

"Warn on close" for multiple tabs no longer works in 63.0.3, Firefox just quits without asking

  • 1 个回答
  • 1 人有此问题
  • 15 次查看
  • 最后回复者为 milescederman

more options

I'm running 63.0.3 on OS X and just noticed that if I quit (either with command-Q or Firefox->Quit) it will just quit out automatically and not prompt a warning. I've double checked all "warn on close" settings through about:settings, tried toggling them, got the "Warn on close" setting to show up in the security preferences panel and toggled it there - nada. Multiple windows, same thing. Am I alone in this?

I also noticed recently that on Firefox across devices that my "restore previous session" setting was toggled off on upgrade, but at least that is fixed by reenabling it.

I'm running 63.0.3 on OS X and just noticed that if I quit (either with command-Q or Firefox->Quit) it will just quit out automatically and not prompt a warning. I've double checked all "warn on close" settings through about:settings, tried toggling them, got the "Warn on close" setting to show up in the security preferences panel and toggled it there - nada. Multiple windows, same thing. Am I alone in this? I also noticed recently that on Firefox across devices that my "restore previous session" setting was toggled off on upgrade, but at least that is fixed by reenabling it.

被采纳的解决方案

Soon after I posted this I found this Reddit thread: https://www.reddit.com/r/firefox/comments/9rt1kn/how_to_get_a_warning_when_closing_firefox_and/

And this bug: https://bugzilla.mozilla.org/show_bug.cgi?id=550559

So I think it's being looked into. I found the "disable cmd-q" plug-in linked to in the reddit thread very helpful as a workaround.

定位到答案原位置 👍 0

所有回复 (1)

more options

选择的解决方案

Soon after I posted this I found this Reddit thread: https://www.reddit.com/r/firefox/comments/9rt1kn/how_to_get_a_warning_when_closing_firefox_and/

And this bug: https://bugzilla.mozilla.org/show_bug.cgi?id=550559

So I think it's being looked into. I found the "disable cmd-q" plug-in linked to in the reddit thread very helpful as a workaround.