Avatar for Username

Mozilla Support में खोजें

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

This thread was archived. Please ask a new question if you need help.

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

  • 1 प्रत्युत्तर दें
  • 1 यह समस्या है
  • 4 views
  • के द्वारा अंतिम प्रतियुतर 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.

चुने गए समाधान

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.

संदर्भ में यह जवाब पढ़ें 👍 0

All Replies (1)

spinor87
spinor87 प्रश्नकर्ता
more options

चयनित समाधान

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.