Avatar for Username

Sök i support

Akta dig för supportbedrägerier: Vi kommer aldrig att be dig att ringa eller skicka ett sms till ett telefonnummer eller dela personlig information. Rapportera misstänkt aktivitet med alternativet "Rapportera missbruk".

Läs mer

Denna tråd har arkiverats. Ställ en ny fråga om du behöver hjälp.

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

  • 1 svar
  • 1 har detta problem
  • 4 visningar
  • Senaste svar av spinor87

spinor87
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.

Vald lösning

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.

Läs svaret i sitt sammanhang 👍 0

Alla svar (1)

spinor87
spinor87 Frågans ägare
more options

Vald lösning

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.