搜尋 Mozilla 技術支援網站

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

Learn More

The open new tab (+ sign button) unexpectedly stopped working when I click on the + sign why?

  • 3 回覆
  • 4 有這個問題
  • 13 次檢視
  • 最近回覆由 cor-el

more options

The + sign button that opens a new tab (called Untitled) stopped working. When I go to File, and click on New Tab, that does not work either. I checked the Options and made sure the "Open new window in new tab instead was checked. I tried System Restore, and I downloaded and installed Firefox 5.0. The + sign still does not work. This problem in on my desktop. I checked my laptop and the open new tab + sign button is working fine. What is happening?

The + sign button that opens a new tab (called Untitled) stopped working. When I go to File, and click on New Tab, that does not work either. I checked the Options and made sure the "Open new window in new tab instead was checked. I tried System Restore, and I downloaded and installed Firefox 5.0. The + sign still does not work. This problem in on my desktop. I checked my laptop and the open new tab + sign button is working fine. What is happening?

所有回覆 (3)

more options

Start Firefox in Diagnose Firefox issues using Troubleshoot Mode to check if one of the extensions is causing the problem (switch to the DEFAULT theme: Firefox (Tools) > Add-ons > Appearance/Themes).

If it does work in Safe-mode then disable all extensions and then try to find which is causing it by enabling one at a time until the problem reappears.

  • Use "Disable all add-ons" on the Safe mode start window to disable all extensions.
  • Close and restart Firefox after each change via "File > Exit" (Mac: "Firefox > Quit"; Linux: "File > Quit")

In Firefox 4+ you can use one of these to start in Safe mode:

  • Help > Restart with Add-ons Disabled
  • Hold down the Shift key while double clicking the Firefox desktop shortcut (Windows)

more options

Hi, Cor-el,

Thank you so much. Your solution worked perfectly. Gosh, so much distress that was quickly resolved when I read and implemented your "fix." Thanks again!

more options

You're welcome

Can you tell us which Add-on caused the problem or how you otherwise solved it?
It helps others who read this thread.