Default container for opened external links

External links are now opened in the same container you were in when clicking on the link, so for example if you have Google container, sites opened from search results page end up in Google container too. Would be nice to have an option to set default container (like No container or Untrusted or random new container (like with Click To Contain extension)).

[rmenessec]

Seconded: I would really appreciate a mechanism to prevent sites without matching rules from opening in any container at all.

For example: I use a feed reader service. I have a rule set in Containerise so that Newsblur always opens in a container dedicated to Newsblur. When I click an outgoing link (destination other than newsblur.com) to read a “full article” (the original web page associated with a feed entry), I don’t want the outgoing link to open in the container for Newsblur.

Currently, the only way I can do that is to set up a huge number of containers and associated rules for all the news sites whose feeds are aggregated on Newsblur. This defeats the purpose of having a container for Newsblur in the first place.

[rmenessec]

@heussd, thanks for pointing that out.

Personally, I’m getting ready to disable Containers if neither Containerise nor Firefox Multi-Account Containers are going to fix this problem. And it really is a problem: there’s no point in opening every Facebook URL (for example) in a Facebook container or a Google URL in a Google container if other sites’ data are going to pollute the containers. That defeats the whole purpose of doing this in the first place.

Because of this severe limitation, I’m not seeing any real benefit from containers. What I’m seeing instead are bugs where both this extension and the Mozilla one sometimes fail to open configured domains / URLs in containers some of the time, isolating my login credentials (cookies, DOM storage, etc.) in one container, with some tabs for the same site opening in another container, but minus the login state.

Containers are a great idea in theory, but the implementation—and the extensions I hoped would fix it—are clearly immature at this point.