Avatar for Username

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Learn More

Dieses Thema wurde archiviert. Bitte stellen Sie eine neue Frage, wenn Sie Hilfe benötigen.

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

  • 2 Antworten
  • 0 haben dieses Problem
  • 14 Aufrufe
  • Letzte Antwort von 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?

Alle Antworten (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 Fragesteller
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.