New Mode: Every site is a container

[ajvsol]

This mode takes advantage of containers privacy advantages to prevent any domain from knowing about other domains the user has accessed.

UX-wise I picture it being implemented as an on/off button in the toolbar which turns it on for the tab you're on. This then causes every link to 3rd-party domains followed in this tab to become new containers.

This is especially helpful to use on search engines, directories etc whereas you'd likely need to be avoid this mode if you're making an ecommerce transaction as there might be redirects to 3rd-party payment sites (much like temporarily turning off the cross-site scripting filtering of extensions like NoScript).

Related:

• Consider making Add-on settings container-specific #309
• An extension of the 'Site-specific Containers' idea in the Mozilla Wiki

┆Issue is synchronized with this Jira Task

[jonathanKingston]

The major problem I see with this right now is that if we created a container per site these would all be added to the menus etc which would be pretty intrusive. Other than that I think the idea is pretty solid.

We have spoken about having hidden containers which would solve the issue of cluttered menus.

[keeferrourke]

+1 This would be an excellent feature! Whether or not this would implemented as "hidden" containers, I think that having the ability to sandbox every tab would be super useful for privacy-minded individuals.

[physkets]

Additionally, an option to make this the behaviour of 'default' tabs would be nice. This is for a use-case where once one has sorted all their tabs into containers, anything more they open should see nothing else.

[groovecoder]

This is effectively what first-party isolation does. Though I really like the idea of enabling first-party isolation everywhere ELSE, OUTSIDE of containers. Seems like an interesting way for people to control which sites to bundle together, and treat the rest of the web with a bit more caution.

[ArchangeGabriel]

So I think what I need is first-party isolation + some way to have different profiles for the same websites (because I might want to browse without being logged or log-in with different accounts).

In that regard containers would just be a way to have several contexts for the same website. Question is whether I would need a container per web-site or whether I could be adding several websites to the same container while still keeping first party isolation between them?

My use case would be for instance browsing shopping sites without being logged to avoid tracking of the objects I look at, and then later (different hour, IP —tor?—, etc… to avoid at the maximum direct linking between the two browsing sessions) open a tab in my shopping container and get rather straight to the object of my interest without looking at other ones. Or even buy it offline or on another website. :p