Multi-account-containers: Feature Request: Option to automatically exit container

[antoni-k]

This is a feature request for an option that would allow a container to act much like the Facebook Container extension - it would only activate when a listed site is opened, and deactivate when you navigate to a site which is not on that list.

[antoni-k]

Something like this addon would be great, if it would actually work.

[SamSirry]

With this requested feature, following links from Facebook may still expose you, because Facebook appends the ClientID to the URLs which you click to from its site, and when you land on another container, trackers can link this container with the Facebook container, defeating the usefulness of using containers in the first place.
P.s.: Even if you disable 3rd party cookies, that doesn't help. However, disabling trackers might help.

[Dormann]

With this requested feature, following links from Facebook may still expose you, because Facebook appends the ClientID to the URLs which you click to from its site,

Then, all you need is an option to allow sanitization of URLs like these addons do :

• https://addons.mozilla.org/en-US/firefox/addon/link-cleaner/
• https://addons.mozilla.org/en-US/firefox/addon/clean-links-webext/

In fact, this would be very intersting if paired with the feature request #691 (Always open URLs that match a pattern in a container).

[mikepurvis]

I think what this request boils down to is that there are two mental models of what a container is— there are site containers (like Google, Facebook, etc) and session containers (private browsing is like this).

Right now the extension treats everything as a session container that you stay in unless you explicitly choose to leave it when opening a link in a new tab. But IMO this isn't the right behaviour. The default should be the _site container_ which allow me to supply a list of URL patterns that will always open in the named container, and where any links which are opened from within that container and don't match the list are instead opened in a private, temporary, or non-container tab.

Session containers may well have a use too, but if both are supported, the distinction should be clearly called out.

[kendallcorner]

Hi. This looks like a duplicate of #914. Please vote (:+1:) or discuss on that issue to show your interest. I'll close this, but feel free to request a reopen if you think it's a different issue.