Funkcionalnosć tutoho sydła so přez wothladowanske dźěła wobmjezuje, kotrež maja waše dožiwjenje polěpšić. Jeli nastawk waš problem njerozrisuje a chceće prašenje stajić, wobroćće so na naše zhromodźenstwo pomocy, kotrež na to čaka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomhać.

Pomoc přepytać

Hladajće so wobšudstwa pomocy. Njenamołwimy was ženje, telefonowe čisło zawołać, SMS pósłać abo wosobinske informacije přeradźić. Prošu zdźělće podhladnu aktiwitu z pomocu nastajenja „Znjewužiwanje zdźělić“.

Dalše informacije

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

  • 2 wotmołwje
  • 0 ma tutón problem
  • 1 napohlad
  • Poslednja wotmołwa wot 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?

Wšě wotmołwy (2)

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.

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.