I've found the behavior with a lot of the native controls that open tabs from the current page to act very inconsistently with tree tabs and containers - some will open sibling tabs instead of children, some will ignore the current container and instead use the default, and some will do both. When just opening tabs regularly it seems pretty consistent.
Not applicable in safari, but it doesn't match my expectations, or the behavior of FF containers and the sideberry plugin.
I have both tree tabs and have just one container set up (plus the default of no container).
Examples:
- cmd-clicking the back button will open a child tab if it already has children but a sibling if not, and it uses no container, even if the current tab has a container applied
- using the 'open image in new tab' context menu button will open as a child, but use no container, even if the current tab has a container applied
- On the start page, opening in a new tab will always open the tab at the top level with no container, even if i've opened the start page with a container (helpful for quickly opening a bunch of pages i have in my faves)
I would guess there's more cases but these are the ones i could find when auditing after i noticed the weird behavior.
I love that containers are now native - having both them and tree-tabs was what kept me on FF with extensions forever. Thanks for adding these features!
For the cases described above, with tree tabs and one container set up i expect:
- cmd-clicking the back button with tree tabs should always open a child, and it should always be the same container that the current page is in.
- using the 'open image in new tab' context menu button should continue to open as a child, and should always be the same container as the page you opened from
- On the start page, opening in a new tab should open the page as a child and with the same container.
Realistically this behavior should be the same for any case that opens a new tab from the current page - make it a child, make it the same container.
Orion 1.1.2 (151), macOS 15.7.3
Sequoia (15)
Edit 2026-09-06:
found another case - highlighting a url, the context menu "go to https://.... in new tab" will correctly make a child tab, but it ignores the container