-
Notifications
You must be signed in to change notification settings - Fork 340
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow per-container privacy settings #318
Comments
This would be a great feature. "Private browsing mode" could then just be a specialised undeletable container. |
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. |
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. |
Maybe at the top of the history sidebar and privacy settings page there could be a dropdown menu, with something like: |
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. |
I don't know which issue should remain, as there are probably dupplicates between this current one, and #47 and #48
|
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 Is it possible to have per account settings for individual plugins? |
@rodneyrod Not yet, that is exactly what #309 is about. |
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). |
@geotheory I've been using Cookie Auto Delete extension, which does pretty much the same thing on a per-container basis. |
Not seeing any progress here. Is this something maintainers would accept a PR for? |
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).
|
The ability to enable first-party isolation per container would be fantastic. I can imagine other settings being useful, too, e.g. tracking protection.
The text was updated successfully, but these errors were encountered: