This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

Buscar en Ayuda

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.

Learn More

Este tema ha sido archivado. Haz una nueva pregunta si necesitas ayuda.

Quite suddenly, in vsn 3.6.16, the "New Tab" icon (the + sign) has stopped working... cannot open new windows in FoxFire. Did something change?

  • 2 respuestas
  • 11 tienen este problema
  • 1 visita
  • Última respuesta de davidinct

davidinct
davidinct
more options

Running Vista Home on a Sony Vaio. Everything was fine with FireFox 3.6.16 up until today when, quite inexplicably, I can no longer open new tabs using the "+" icon. FireFox still supports multiple tabs... right now, my Home page is open, and this FireFox Help option opened up its own new tab. Cannot for the life of me figure out what has changed. (And yes, have already done the Reboot sequence... to no avail.)

Running Vista Home on a Sony Vaio. Everything was fine with FireFox 3.6.16 up until today when, quite inexplicably, I can no longer open new tabs using the "+" icon. FireFox still supports multiple tabs... right now, my Home page is open, and this FireFox Help option opened up its own new tab. Cannot for the life of me figure out what has changed. (And yes, have already done the Reboot sequence... to no avail.)

Todas las respuestas (2)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

This issue can be caused by the Ask.com toolbar (Tools > Add-ons > Extensions)

See:

davidinct
davidinct Autor de la pregunta
more options

Disabled a toolbar - not the Ask one, but one (Webroot) that had Ask search capability embedded in it. Rebooted FoxFire, and it's now working correctly once again.

Thanks, cor-el for your insight.

David (in CT)