Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Avatar for Username

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

Tuta nitka je so archiwowała. Prošu stajće nowe prašenje, jeli pomoc trjebaće.

Much too easy to tear tabs

  • 2 wotmołwje
  • 1 ma tutón problem
  • 51 napohladow
  • Poslednja wotmołwa wot Moff

Moff
Moff

Hi, this has been happening for a while now, and is very frustrating - it's much too easy to tear off tabs into new a new window; the tinyest drag whilst the left mouse button is clicked is enough to pull the tab into a new window; I've tried turning off tear tab behaviour, but that is more annoying than the tabs tearing itself, since it doesn't stop the action, it just means that the tab doesn't go to a new window but stays where it is, after messing with Tree Style Tab a bit (it removes the tab from any tree its in, and bugs the tree so it won't accept new child tabs). That setting also stops you moving a tab to a new window at all - you have to copy the url and open a new window and navigate to the URL.

Any idea what might be happening? I've searched several times over the last few months and the only hits I get are 4 years old (and recommend turning off tab tearing at all).

Thanks,

Hi, this has been happening for a while now, and is very frustrating - it's much too easy to tear off tabs into new a new window; the tinyest drag whilst the left mouse button is clicked is enough to pull the tab into a new window; I've tried turning off tear tab behaviour, but that is more annoying than the tabs tearing itself, since it doesn't stop the action, it just means that the tab doesn't go to a new window but stays where it is, after messing with Tree Style Tab a bit (it removes the tab from any tree its in, and bugs the tree so it won't accept new child tabs). That setting also stops you moving a tab to a new window at all - you have to copy the url and open a new window and navigate to the URL. Any idea what might be happening? I've searched several times over the last few months and the only hits I get are 4 years old (and recommend turning off tab tearing at all). Thanks,

Wšě wotmołwy (2)

Moff
Moff Prašer

> I've tried turning off tear tab behaviour, but that is more annoying than the tabs tearing itself, since it doesn't stop the action, it just means that the tab doesn't go to a new window but stays where it is, after messing with Tree Style Tab a bit (it removes the tab from any tree its in, and bugs the tree so it won't accept new child tabs). That setting also stops you moving a tab to a new window at all - you have to copy the url and open a new window and navigate to the URL.

FYI my broken TST behavior was caused by a "disable tab detach" extension that does not play nicely with it.

Having disabled this "disable tab detach" TST behaves sensibly again, however "browser.tabs.allowTabDetach" simply does not work - true or false you can always drag a tab to detach it.

Anyone had similar problems?

Cheers

Moff
Moff Prašer

Have found the solution (and the cause of the problem): browser.tabs.allowTabDetach only works for horizontal tabs along the title bar - sidebar managed tabs are unaffected.

The solution is to go to the "drag and drop" settings in TST and change it to "do nothing". This combined with browser.tabs.allowTabDetach stops tabs being dragged into new windows accidentally.

You can still right-click "move to new window".

Would be nice to know why tab tearing is so sensitive these days, and why you can't change the required drag distance for detach, but for now this solution works for me.

(Also don't use add-ons that try and change tab detach behavior at the same time as side-bar managed tabs).