I have set TST to append new child tabs at the bottom of the tree. That works as expected.
However, when I open a new Tab using the Temporary Container extension, it puts it at the top of the tree instead. I see no option in the Temporary Container extension to control the Tab position. Can this be controlled by TST?
I couldn't reproduce the problem. Steps I did:
https://piro.sakura.ne.jp/latest/.At the step 7, opened tabs are opened as last child of the active tab for me. Any difference about configurations of TST itself and Temporary Containers?
I reproduced what you wrote above except when I middle-click (on my mouse) a new temporary container opens. Why is that?
The difference with our setups is otherwise that I don't use Automatic mode (it is unchecked)!
In this case, regular (non-container) tabs opens as children at the bottom of the tree, while container tabs open at the top of the tree (I select to open the Tab in a temporary container by right-clicking).
Ah, I got it. I didn't know how to open tabs in temporary containers without the automatic mode, and I finally understood that there is a context menu command "Open link in new Temporary Container tab". After I disabled the automatic mode and opened links from the command, I've successfully reproduced this problem.
I've looked the debug log. What happens when a new temporary container tab is opened from the context menu command is:
On the other hand, if you middle-click on a link:
So I think Temporary Containers needs to specify the opener information for a new tab.
I've created a pull request to do that on Temporary Containers side.
The PR has been merged, so this issue will be fixed with the next release of Temporary Containers.
Great. Thanks!
I will close this after testing the new version of Temporary Containers.
@viking2 has the new version been released? Can you close this item if resolved?
@irvinm,
No, a new version has been released yet :-(.
@stoically this pull request has been merged into Temporary Containers since October 9th. Any chance you could produce a point release to verify this has been fixed?
@viking2 may I suggest closing this item for now? There isn't anything more that can be done on the TST side now and if the pull request doesn't fix the issue long term you can always reopen this issue.
@piroor @irvinm Sorry for the delay, released TC 1.9.2, thanks for the PR!
Works now. Thanks!