Skip to content
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

Clear cookies/localStorage at the end of the session per-container setting #48

Open
nt1m opened this issue Jan 9, 2017 · 13 comments
Open
Labels
👍 Feature Request Feature requests users would like to see in this addon

Comments

@nt1m
Copy link

nt1m commented Jan 9, 2017

It would be nice if we could configure a container to auto-clear cookies/localStorage at the end of session. This is especially useful for the Shopping container, where travel booking websites track to give you a different price for the same trip everytime you search (national express is a good example).

@nt1m
Copy link
Author

nt1m commented Jan 9, 2017

A more useful feature for the specific use-case I've mentioned would be clearing cookies/localStorage periodically.

@johngruen johngruen modified the milestone: Stretch Jan 19, 2017
@groovecoder groovecoder removed this from the Stretch milestone Apr 28, 2017
@danemacmillan
Copy link

danemacmillan commented Jun 2, 2017

I would very much like to see the entire "Privacy & Security" setting be container-relative. In other words, the top-most option on that page should be the container name where the below settings are applied. That would simplify the UI and make it very clear how settings are configured per container. It really should be the parent option to all these settings. This would provide immense control and granularity, which is the goal of the container experiment.

@apkd
Copy link

apkd commented Oct 21, 2017

This is a feature I looked for immediately after I started using containers. A long time ago I have learned to instinctively launch private mode whenever I do research online (I don't want a million tracking cookies associated with my browser instance from random websites opened for a few seconds while searching). This however presents various usability problems. Containers are an excellent solution - I assign ddg/google to a dedicated container, and whenever I navigate to a website I consider secure, the site switches to the personal container. However, cookies and browsing history still get permanently associated with the "throwaway search" container, and an option to have them automatically purge (preferably, with an ability to whitelist domains) would make this perfect for my use case.

@msanders
Copy link

This would be a great feature, especially for the default container.

@max-dw-i
Copy link

It's been almost 4 years. The most important container feature is still not here :(

@dorfsmay
Copy link

For this very reason I have given up on containers and am now using different profiles, clearing cookies when closing the last window/tab of a given profile.

@dannycolin dannycolin added 👍 Feature Request Feature requests users would like to see in this addon and removed enhancement labels May 20, 2022
@KaXaSA
Copy link

KaXaSA commented Oct 24, 2023

I would like to have an option in the container to remove the cookies, storage, etc. once you close the tab/container.

@influential-eliot
Copy link

So, essentially containerised private browsing.

Wholly support. Would allow us to make multiple private sandboxes.

@anewuser
Copy link

anewuser commented Aug 14, 2024

You may like this extension: Open in Temp Container. It lets you add rules to always open certain domains in disposable containers. You can also set it not to record your browsing history.

@apkd
Copy link

apkd commented Aug 20, 2024

You may like this extension: Open in Temp Container. It lets you add rules to always open certain domains in disposable containers. You can also set it not to record your browsing history.

The last time I tried to use this/similar extension, I ended up with hundreds of containers that it didn't clean up. I only noticed when my browser installation slowed down to a crawl. I think I ended up having to nuke my browser profile, because Firefox doesn't have the option to mass-delete containers.

Anyway, this is the inverse of the functionality I actually want. I wish all pages opened in a temp container by default, with the few whitelisted websites allowed to persist cookies.

Last time I tried containers, they were annoying to work, introduced lots of working parts that you need to keep track of, various edge cases and glitches, etc. Honestly, they seem like a huge overkill abstraction compared to the simple workflow I wish was possible: "incognito by default with per-domain opt-out".

@anewuser
Copy link

anewuser commented Aug 20, 2024

This wasn't the extension that caused you issues, and it includes the exact options you are looking for.

@apkd
Copy link

apkd commented Aug 20, 2024

I'll give it a try then, thanks

@kdoteu
Copy link

kdoteu commented Sep 4, 2024

This wasn't the extension that caused you issues, and it includes the exact options you are looking for.

It seems you are right with this suggestions. But I prefer to reduce my installed extensions and it would be perfect if this feature would be integrated in an offical extension.

At this moment I solved this "issue" by adding different temp-enviroments and after closing my browser every session is cleared. But I need to remember which temp-env is already used.

For my purpose it would be great to have all sessions data cleared (confugurable) when the last enviroment tab is closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
👍 Feature Request Feature requests users would like to see in this addon
Projects
None yet
Development

No branches or pull requests