Allow per-container privacy settings

mozilla / multi-account-containers

Firefox Multi-Account Containers lets you keep parts of your online life separated into color-coded tabs that preserve your privacy. Cookies are separated by container, allowing you to use the web with multiple identities or accounts simultaneously.

https://addons.mozilla.org/firefox/addon/multi-account-containers/

Mozilla Public License 2.0

2.71k stars 341 forks source link

Allow per-container privacy settings #318

Open amluto opened 7 years ago

amluto commented 7 years ago

The ability to enable first-party isolation per container would be fantastic. I can imagine other settings being useful, too, e.g. tracking protection.

rikkit commented 7 years ago

This would be a great feature. "Private browsing mode" could then just be a specialised undeletable container.

groovecoder commented 7 years ago

You're right that PBM is, in a sense, a container in which tracking protection is enabled, cookies and history are deleted on close, etc.

biva commented 7 years ago

In addition, like suggested in https://discourse.mozilla-community.org/t/custom-history-settings-for-each-container/14485/3 , it would be great to delete history / cookies / connections per container

kjozwiak commented 7 years ago

In addition, like suggested in https://discourse.mozilla-community.org/t/custom-history-settings-for-each-container/14485/3 , it would be great to delete history / cookies / connections per container

Bug#1199470 would address clearing history per container.

imyxh commented 7 years ago

In addition, like suggested in https://discourse.mozilla-community.org/t/custom-history-settings-for-each-container/14485/3 , it would be great to delete history / cookies / connections per container

Maybe at the top of the history sidebar and privacy settings page there could be a dropdown menu, with something like: Edit settings for: ▼ Default container Personal (example) Shopping (example) etc. I suppose this is really a pointless suggestion you would've arrived at anyway, but hey. Of course, "edit settings for" could be replaced with "showing history for" or whatever else is relevant.

b0urb0n commented 6 years ago

As @biva mentioned, the ability to remove cookies and history on a per-container basis would be very useful. Currently, there is no way to individually "clean-up" a contaminated container.

biva commented 6 years ago

I don't know which issue should remain, as there are probably dupplicates between this current one, and https://github.com/mozilla/multi-account-containers/issues/47 and https://github.com/mozilla/multi-account-containers/issues/48 I understand that there are 2 needs:

have different settings per container (this current issue)
be able to clear navigation data per container (including history https://github.com/mozilla/multi-account-containers/issues/47, cookies and all other stuff accesible with Ctrl+Shift+Delete) @jonathanKingston : which issues should we keep to have 1 (or 2) common place to discuss?

captn3m0 commented 6 years ago

In addition to the above cookie settings, I'd also like to see a "disable javascript" setting for a container. I'd want to disable javascript (and cookies) on my Default container. Any application that requires either can go into my Personal/Work containers.

ArchangeGabriel commented 6 years ago

@captn3m0 That could be done with uMatrix or NoScript + #309.

rodneyrod commented 6 years ago

@ArchangeGabriel Is it possible to have per account settings for individual plugins?

ArchangeGabriel commented 6 years ago

@rodneyrod Not yet, that is exactly what #309 is about.

geotheory commented 6 years ago

Another option I'd love to see that might prove popular would be a container policy to accept cookies for all sites but delete them as soon as the site's last tab is closed (vs when browser is closed).

captn3m0 commented 6 years ago

@geotheory I've been using Cookie Auto Delete extension, which does pretty much the same thing on a per-container basis.

willlma commented 4 years ago

Not seeing any progress here. Is this something maintainers would accept a PR for?

Dannniello commented 4 years ago

@geotheory I've been using Cookie Auto Delete extension, which does pretty much the same thing on a per-container basis.

Unfortunately Cookie AutoDelete cannot remove localStorage per container. Only "old fashioned" cookies could be removed per container...

It is better than nothing, but nowadays many sites are using cookies and localStorage in the same time. In very short: localStorage is something like cookies, but could store much more data.

Firefox is not supporting removing localStorage per container - it means that you could remove all localStorage or nothing (for example removing youtube.com localStorage in "Default" container will also remove YouTube settings in "Google YouTube" container).

https://github.com/Cookie-AutoDelete/Cookie-AutoDelete/wiki/Documentation#enable-localstorage-support

"The API for localstorage cleaning doesn't appear to support Containers. So if cookies from one container are cleared, then all of the site's localstorage from all containers are deleted regardless of whitelisting rules."