Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Avatar for Username

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

Since new update, new tabs open behind current tab instead of behind marked tabs

  • 2 replies
  • 0 have this problem
  • 1 view
  • Last reply by Sneed

Sneed
Sneed
more options

Hey there!

Since the newest update (I think), whenever I select multiple tabs and attempt to open a new one via pressing the middle mouse button (or the MMB together with shift), the new tab opens behind the current open tab instead of the marked tabs.

For example: If I mark two tabs and have the left tab open, pressing the MMB on the + symbol would normally open a new tab to the right of those two tabs. Now, however, it opens the tab inbetween the two selected tabs.

Is there a way to change this back?

Hey there! Since the newest update (I think), whenever I select multiple tabs and attempt to open a new one via pressing the middle mouse button (or the MMB together with shift), the new tab opens behind the current open tab instead of the marked tabs. For example: If I mark two tabs and have the left tab open, pressing the MMB on the + symbol would normally open a new tab to the right of those two tabs. Now, however, it opens the tab inbetween the two selected tabs. Is there a way to change this back?

All Replies (2)

zeroknight
zeroknight
more options

Multiple selected tabs no longer affects where tabs open since version 115 (Bug 1791231). An extension could possibly replicate the old behavior but it is highly specific.

Sneed
Sneed Question owner
more options

zeroknight said
Multiple selected tabs no longer affects where tabs open since version 115 (Bug 1791231). An extension could possibly replicate the old behavior but it is highly specific.

Ah, I see. So is that a bug that will be fixed in the future, or did Mozilla think that it was a bug and ""fix"" it? Either way, thank you for the information.