[sirmoveon]

You are right the user experience is chunky and not self explanatory. But what you are trying to achieve is possible. Play with the settings a bit. I have it in a way that if I type a domain that is assigned to a container, it will ask me first if I want to open it in its default container or a different one.

[Tomte]

That's not what he (and I and many others) are asking for.

The site linked to is not assigned to any container. It opens in the old container, while it should open in the default container.

[sirmoveon]

I'm just trying to help.

The idea of having a link clicked inside a container and expect it to go to a different container as a default setting, seems to contradict web standars. Now, if you've explicitly assigned the clicked domain to a different container, then yes, it should go to its container (which is how it works, to me at least).

[Tomte]

I'm simply explaining something you hadn't understood.

But I'm not aware of any "web standard" codifying container behaviour.

[danlugo92]

There are (standarized) things that get sent to x.com when you click on a link to it on m.com. Stuff that wouldn't be there if you actually copy pasted the link.

[Tomte]

Referer? Great.

What does that have to do with containers, or better, why do you believe what many users want is forbidden by "web standards"?

[StavrosK]

> seems to contradict web standars

But if I click a Google link, it already goes to a different container (the Google one), because I've told it to.

> Now, if you've explicitly assigned the clicked domain to a different container, then yes, it should go to its container

I am trying to assign "all non-google.com links" to open in the default container.