My workflows embrace rich, seamless movement – as is possible with combinations of extensions such as these:
We wrote a whole wiki response on why primary container UI doesn’t want to support this: https://github.com/mozilla/multi-account-containers/wiki/Moving-between-containers
I think we should concentrate on providing UI flows that are useful for promoting users into making themselves more private. I don’t fully think we are there yet and we want to keep iterating on this. However this seamless movement you speak of simply isn’t possible in privacy conscious world.
However this doesn’t prevent other add-ons from implementing this on top of containers however I don’t think this will ever become core UI.
What if the transitioning tab – with e.g. four transitions3 or more – is one of fifty tabs or more?
I don’t think switching tabs is really switching contexts, we are merely talking improving the tab UI itself in that bug. For example container assignment changes a tab from one container to another on redirection. Sure Conex can decide to use that for tab switching URLs but they already can do this by swapping a tab out to a new one, it just looks a little uglier than desired.
I disagree that tab management isn’t possible especially as there are already lots of extensions out there solving these issues.