Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Learn More

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

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

  • 1 antwurd
  • 1 hat dit probleem
  • 50 werjeftes
  • Lêste antwurd fan 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.

Keazen oplossing

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.

Dit antwurd yn kontekst lêze 👍 0

Alle antwurden (1)

more options

Keazen oplossing

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.