[Bug] (Tabs opened from existing tabs get moved to the end of a tree regardless of chosen option.)

[Bluetinity]

[Bug] (Tabs opened from existing tabs get moved to the end of a tree regardless of chosen option.)

[piroor]

The option you saw is for tabs opened from pinned tabs. You should see another option for your purpose: TST options => "Tree Behavior" => "Insertion position of new child tabs". It affects to general cases including "tabs are opened from a non-pinned tabs" and "tabs are drag-and-dropped onto a tab".

BTW I agree the categorization is user-unfriendly. Hmm, is it the time to add one more option to the "tabs opened from Existing Tabs" section...

[piroor]

Ah, I missed an existing option. With activated "expert options", you'll see an option "Tabs opened from Existing Tabs" => "When a tab is opened from existing tab, open it as". It is "a child of the parent tab" by default and you can choose "a child of the parent tab, next to the recently opened child" to change the insertion position of new child tabs.

However it does not allow you to insert new child tab at the top of children - you need to configure "Tree Behavior" => "Insertion position of new child tabs". In other words, currently there are two separate options but they are partially overlapped.

[piroor]

I've restructure options with the commit e08d8df.
Now TST has choices "open new tab as first or last child" explicitly for each "open tab as..." options. Your case is now covered with an expert option "Tabs opened from Existing Tabs" => "When a tab is opened from existing tab, open it as" and you don't need to configure more other options.

[piroor]

I've seen some unexpected results with edge cases: tabs from a pinned parent are unexpectedly attached as first child of the alias group-tab tree. Configs:

• New tabs from existing tab = opened as last child
• New tabs from pinned parent = near last related tab or near the parent

It looks that I have to do more.

[Bluetinity]

Well thanks for the info, it fixes the problem I had. I guess i just didn't understand what all the options did. You can close the issue now or later if you want to address those edge cases first.

[github-actions]

This issue has been closed due to no response within 14 days after labeled as "fixed", 7 days after last reopened, and 7 days after last commented.