All other trees collapse when dragging a tab on top of other tabs, except for the tree where the tab is being dragged to.
On TST welcome page, check option for "Don't expand collapsed tree and skip collapsed descendants, while switching focus of tabs via keyboard shortcuts (requires script injection to webpages for detection of keyboard operations)"
uncheck option for "Except focus moving caused by closing of the current tab"
Create Tree Structure:
Parent 1
Child 1
Parent 2
Child 2
Parent 3
Child 3
Parent 4
Lone Tab 1
There may be other situations where this is repeatable as well, that I have not tested.
FYI, behavior does not happen dragging and hovering between Parent or Child, or between Parents, or above Parents or below Parents, IE: not on top of a tab
Expecting all tree structure to stay expanded when dragging and hovering Lone Tab 1 to any location for any time duration
Tree structure collapses for all trees except where Lone Tab 1 is being dragged


TST needs a setting that says do not collapse/expand at all, if possible, if it makes sense. If it can be respected, then it would provide predictability to the user. As it is now, this collapsing behavior can cause visual confusion and disruption of user workflow when the user gets lost where they were in the tree structure. It can be especially disorienting if their tree structures are very complex.
In the confusion, one may accidentally drop the tab somewhere and not be able to find it, if the tree structure is very complex and lots of parents are collapsed, causing a large vertical displacement in position of all the tabs when this unasked-for collapsing behavior occurs.
An example in a complex tree shows the large vertical displacement and likely confusion:

same here its very annoying, ( i have thousand tab)
also when i enable debug mode, the option page disapear completly
is 3.0.4 version have this issue also?
i want to downgrade
Thanks, this odd behavior should be fixed with the commit 60e5e81. Now TST just ignores already expanded tree on such cases.
Whew! I thought I was losing my mind! Thanks @azizLIGHT for reporting it and of course @piroor for a quick fix!
Fixed for me on 3.0.6. Thanks
Most helpful comment
Thanks, this odd behavior should be fixed with the commit 60e5e81. Now TST just ignores already expanded tree on such cases.