Avatar for Username

Търсене в помощните статии

Избягвайте измамите при поддръжката. Никога няма да ви помолим да се обадите или изпратите SMS на телефонен номер или да споделите лична информация. Моля, докладвайте подозрителна активност на "Докладване за злоупотреба".

Learn More

Тази тема беше архивирана. Моля, задайте нов въпрос ако имате нужда от помощ.

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

  • 2 отговора
  • 0 имат този проблем
  • 14 изгледи
  • Последен отговор от 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?

Всички отговори (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 Задаващият въпроса
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.