Windows 10 will reach EOS (end of support) on October 14, 2025. For more information, see this article.

Avatar for Username

Cerca nel supporto

Attenzione alle mail truffa. Mozilla non chiederà mai di chiamare o mandare messaggi a un numero di telefono o di inviare dati personali. Segnalare qualsiasi attività sospetta utilizzando l'opzione “Segnala abuso”.

Ulteriori informazioni

Questa discussione è archiviata. Inserire una nuova richiesta se occorre aiuto.

New Tab (+) Button Missing...Restore Defaults does NOT work!

jdoll021
jdoll021
more options

Hello,

About a month or so ago, I noticed the New Tab "+" button was missing on the right hand side of the tabs bar. Also missing is the "arrow" for clicking tabs rightward (the left "arrow" for clicking tabs leftward is still present). After a Firefox update today, I had hoped it would come back but it is still missing. I opened "customize toolbars" and clicked "restore defaults" but the New Tab "+" button is not listed as an option! Is this yet another bug that Mozilla claims is a "feature" that no one asked for (like erroneously moving the tabs bar to the top)?

Thanks.

Hello, About a month or so ago, I noticed the New Tab "+" button was missing on the right hand side of the tabs bar. Also missing is the "arrow" for clicking tabs rightward (the left "arrow" for clicking tabs leftward is still present). After a Firefox update today, I had hoped it would come back but it is still missing. I opened "customize toolbars" and clicked "restore defaults" but the New Tab "+" button is not listed as an option! Is this yet another bug that Mozilla claims is a "feature" that no one asked for (like erroneously moving the tabs bar to the top)? Thanks.

Tutte le risposte (1)

jscher2000 - Support Volunteer
jscher2000 - Support Volunteer
  • Top 10 Contributor
more options

Your very last bit makes me think perhaps you are using a userChrome.css file to modify the toolbar area. Perhaps that is related to the problem with the missing buttons?

Your Firefox reported that it is version 128, presumably the Extended Support Release (ESR) version. Or did the problem occur in a newer version and you rolled back to 128 as a workaround?