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.

How to ensure that hyperlinks in pinned tabs open in new tabs?

  • 1 risposta
  • 1 ha questo problema
  • 4 visualizzazioni
  • Ultima risposta di spinor87

more options

I am using Firefox 83.0 (64-bit) on Mac OS Big Sur 11.0.1.

Until recently, when I would click on a hyperlink within a pinned tab, it would open in a new tab. (To be sure, this is *without* pressing the Control key on the Mac, or without right clicking on the mouse --> open link in new tab option).

But now, hyperlinks inside pinned tabs open in the same window. This is a workflow nightmare because I am used to having links originating within my pinned Gmail window open in a new tab.

I have followed the instructions at https://support.mozilla.org/en-US/questions/1283295, but this does not help.

I am using Firefox 83.0 (64-bit) on Mac OS Big Sur 11.0.1. Until recently, when I would click on a hyperlink within a pinned tab, it would open in a new tab. (To be sure, this is *without* pressing the Control key on the Mac, or without right clicking on the mouse --> open link in new tab option). But now, hyperlinks inside pinned tabs open in the same window. This is a workflow nightmare because I am used to having links originating within my pinned Gmail window open in a new tab. I have followed the instructions at https://support.mozilla.org/en-US/questions/1283295, but this does not help.

Soluzione scelta

Following https://support.mozilla.org/en-US/questions/1276852, and setting browser.link.open_newwindow to 3 has apparently "solved" the problem, at least for now.

Leggere questa risposta nel contesto 👍 0

Tutte le risposte (1)

more options

Soluzione scelta

Following https://support.mozilla.org/en-US/questions/1276852, and setting browser.link.open_newwindow to 3 has apparently "solved" the problem, at least for now.