cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Turbofan0879
New member
Status: New idea

The way I see it, Multi-Account Containers has at least two use cases which it does a very good job at.
1: Keep cookies seperated between tabs. For example one container for personal use, one for work.
2: Different tabs via different VPN servers (SOCKS proxies). With this use it makes sense to enable "Delete cookies and site data when Firefox is closed"

I think it would be really interesting to combine these two use cases. By that I mean make some containers automatically clear browsing data, while others remember it.

Then you could have a setup like this:
Container A - No VPN, keep cookies.
Container B - VPN, keep cookies.
Container C - VPN, automatically delete cookies when closing Firefox.
etc.

I think the best way to solve this would be to allow for more fine grained controls over Firefox settings (like the "Delete cookies and site data when Firefox is closed" setting) in each container.
In the meantime, the best workaround I have found is to use "Firefox Browser Developer Edition" for one of the use cases.

3 Comments
Status changed to: New idea
Jon
Community Manager
Community Manager

Thanks for submitting an idea to the Mozilla Connect community! Your idea is now open to votes (aka kudos) and comments.

r_orrison
Strollin' around

Possibly related:

I'd like to have a Junk container that always deletes all cookies whenever the tab is closed.  I'd assign sites like reddit and twitter and some news sites to always open in that container.  It'd be nice if it could also strip tracking information on links that open in the Junk container.

I'd also like to be able to have a container where the cookies for a domain are allowed, but block cookies for that domain in other containers.  For example, have a Google container for my Google account, but block all Google cookies in other containers.  This would be like the Facebook container, but generalized.

cjs
New member

I am an IT admin and i frequently either use private browsing or create a new temporary container for account testing. Having an container that does not retain any cookies would be super helpful in cases like this.