Showing results for 
Show  only  | Search instead for 
Did you mean: 

"new tab" function does not open in bound container context (OSX)

Making moves

If I have click selected a specific tab in a specific container, I have selected a "scope"

I would expect by default, that a "new tab" function (CMD+T on a mac) creates a new tab in that scope.

Instead, it creates a new tab in NO scope.

There should of course BE an "unscoped" new tab function, but surely the default in context of using and enabling containers, is to re-use the local scope not the wider scope?