搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

Learn More

The quit commands (menu selection AND key combination) don't work in Firefox 38

  • 4 回覆
  • 5 有這個問題
  • 12 次檢視
  • 最近回覆由 ender21

more options

When I updated to Firefox 38 the quit commands ceased working. ALT+F4 closes the application as does clicking the X on the title bar but without providing the options to cancel or save the session.

If I disable all add-ons, CTRL+Q closes the application but without providing the options mentioned.

My add-ons include Tab Mix Plus which has a session manager I am using.

I have reinstalled version 37 on my main system but still have version 38 on another system.

When I updated to Firefox 38 the quit commands ceased working. ALT+F4 closes the application as does clicking the X on the title bar but without providing the options to cancel or save the session. If I disable all add-ons, CTRL+Q closes the application but without providing the options mentioned. My add-ons include Tab Mix Plus which has a session manager I am using. I have reinstalled version 37 on my main system but still have version 38 on another system.

被選擇的解決方法

For the record, the problem was caused by interaction with an add-on which has since been updated to fix the problem.

從原來的回覆中察看解決方案 👍 0

所有回覆 (4)

more options

See what happens in the Firefox SafeMode.

more options

What is the current startup setting?

  • Edit > Preferences > General > Startup: "When Firefox Starts":
    "Show my windows and tabs from last time"
    "Show my home page"
    "Show a blank page"
more options

Thank you for the replies.

1. After starting in safe mode CTRL+Q causes Firefox to close without offering the options of cancelling or saving the session.

2. I attach a snapshot of the Start preferences in Firefox, a snapshot of the Tab Mix Plus options for start up and a snapshot of the options I have always had after the quit command.

more options

選擇的解決方法

For the record, the problem was caused by interaction with an add-on which has since been updated to fix the problem.