-
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
[Feature Suggestion] Option to auto remove cookies of a specific container. #1480
Comments
I agree. This should be a high priority feature. Specifically, I would like the ability to clear caches, manage cookies and website data, etc. on a per-container basis. For example, for a container "SearchEngines" I would like to be able to clear all data when I close the last tab of that container. Currently, I have FireFox Preferences configured to clear all data on exit. Rather than having to exit FF, exiting a container should be able to accomplish the same thing. Ideally, opening preferences in a given container should allow the configuration of ALL preferences for that container. For example, I normally proxy all my web traffic through Privoxy. However, it would be VERY nice to be able to configure a container which has different network settings, and maybe even uses a different proxy. Thanks for the great add-on!! |
Agree. Coockies sometimes break in one container only. Would be great if we did not have to clear cookies and other browser data browser wide when this happens. |
Possibly you could accomplish some of what you want with the Cookie Auto Delete(CAD) addon: There is an option to make CAD container aware. |
I have set a specific container for duckduckgo(search engine). And from those search results I visit various websites. Some are familiar and have specific container assigned to them. And some are unfamiliar. These unfamiliar website stores cookies, caches etc.
What I want is, whenever all sites of a specific container is closed, then all cookies, caches etc of that container will be automatically deleted.
Thanks, and keep up the good work!
The text was updated successfully, but these errors were encountered: