Allow to open external links in custom container

[ThisIsFroggie]

The idea is that if a link is rel=external or goes off domain, to have a setting per container to customize if the link is opened by default in the same container or in another one.

The idea is to make it easier to use in two kinds of use cases:

• To make a container more webapp-like and more isolated. A container with my webmail open would open external links in a different container of my choice by default, both preventing tracking, cross-site scripting attempts and even phishing to a certain extent -- if the link leads to a phishing page I can tell from the container description if I am in the same domain or not.
• To browse in content aggregators or social networks such as reddit or Facebook, by opening links from these in an isolated container by default which is not related to the source container.

[jonathanKingston]

This was actually mentioned in my article as follow up tasks: https://jotter.jonathankingston.co.uk/blog/2017/04/04/containers-assignment/

This would potentially break some websites and users expectations around how containers work, however I still think this is a good proposal and certainly something people should vote on.

[jonathanKingston]

Hey @PedroArvela do you think #518 might solve the same use-case? This would be simpler and allow the user to be in control more.

[ThisIsFroggie]

Seems like a reasonable approach. I think it would work for the use case.

[GizmoChicken]

@jonathanKingston If I understand correctly, #518 works sort of like an enhanced version of "right clicking" to select the container (or "no container") into which the linked page will open. Does that sound about right?

If so, then although the feature described in #518 would be a great, for my use case, I would prefer something more like what @PedroArvela originally described. That is, for pages in a given container, I want a way to set, in advance, into what container (or “no container”) a followed link will open, without any need for right clicking the link, or making any other selection when clicking.

To accomplish the above, I hope that the devs will consider providing an option in the “Preferences” page of each container (such as Container X) that will allow setting, in advance, into what container (such as Container X, or Container Y, or Container Z, or “no container”, etc.) a followed link will open.

[deadwax]

I have just started using multi account container after using the Facebook container for a long time. I'm both surprised and frustrated that the behaviour in this feature request isn't the default, it essentially makes the add-on unworkable for me, as I have to constantly check what container I'm in. It's a meta task that I'd rather not train my brain to do (and am unlikely to be successful at)

For whatever reason, the Facebook container works the way you'd expect - you leave the Facebook/Meta world and it spits you out to the default/no container.