3 ms·

This is loosely what Firefox's temporary containers [0] extension does. Each tab (with options to control whether a tab spawned from a parent tab should inherit

by g_p 4y ago

This is loosely what Firefox's temporary containers [0] extension does. Each tab (with options to control whether a tab spawned from a parent tab should inherit the cookie-jar context of the parent) gets its own temporary context. I don't recall whether it clears the jar on navigating away, but you can have that jar cleared when the tab is closed, and you can configure new jars when opening a new tab to a new site origin (i.e. domain). [0] https://addons.mozilla.org/en-US/firefox/addon/temporary-containers/ https://addons.mozilla.org/en-US/firefox/addon/temporary-con...

jeroenhd 4y ago
How well does this extension work together with the Multi-Account Containers addon (https://addons.mozilla.org/en-US/firefox/addon/multi-account-containers/ https://addons.mozilla.org/en-US/firefox/addon/multi-account...)?
- clsec 4y ago
  I've been using both for quite some time now. They work very well together and I don't see myself browsing much without them. edit: remove redundant "together"
  - jeroenhd 4y ago
    I'll give it a go, thanks!
- pavon 4y ago
  It is designed to work with and supplement the Multi-Account Containers add-on. There a few things that are annoying and could use better integration. First, all the temporary containers show up in the list of containers you have created. Most of the time you can ignore that list, so it isn't a big deal, but if you need to configure a permanent container (and you have 100s of tabs open) the clutter makes them harder to find in the long list. When you tell Multi-Account Containers to always open a domain in a specific container, Temporary Containers knows about this, but for some reason it prompts you for additional confirmation. And sometimes this prompt breaks sites the first time through, adding an additional iteration when trying to configure a container to work with a site that uses multiple domains. Other than that they work together fine. I would also recommend the Cookie Quick Manager extension, which lets you manage cookies on a per-container basis. If you have been using Multi-Account Containers by it self, then any links you open from a page will open in the same container (say reading news sites from HN), and you likely have a bunch of cross-site cookies stored there. This extension will let you clear out any undesired third-party cookies that have gathered in the container. The UI is a bit unclear at first (which of these three trashcan icons scattered across the page delete the subset of cookies I want), so read the tooltips before clicking an icon.
pavon 4y ago
I use and love this extension. The main complication that would prevent it from being a mainstream solution to cookie clearing is automating the decision of when to create a new container vs continue to use the existing one when links are clicked. Going by domain name (using Public Suffix List) breaks a lot of SSO implementations, and the occasional payment processor/verification flow, and other situations that redirect to another site, but pass information (or save state to have on return) via cookies.

by g_p 4y ago

jeroenhd 4y ago

How well does this extension work together with the Multi-Account Containers addon (https://addons.mozilla.org/en-US/firefox/addon/multi-account-containers/ https://addons.mozilla.org/en-US/firefox/addon/multi-account...)?

clsec 4y ago
I've been using both for quite some time now. They work very well together and I don't see myself browsing much without them. edit: remove redundant "together"
- jeroenhd 4y ago
  I'll give it a go, thanks!
pavon 4y ago
It is designed to work with and supplement the Multi-Account Containers add-on. There a few things that are annoying and could use better integration. First, all the temporary containers show up in the list of containers you have created. Most of the time you can ignore that list, so it isn't a big deal, but if you need to configure a permanent container (and you have 100s of tabs open) the clutter makes them harder to find in the long list. When you tell Multi-Account Containers to always open a domain in a specific container, Temporary Containers knows about this, but for some reason it prompts you for additional confirmation. And sometimes this prompt breaks sites the first time through, adding an additional iteration when trying to configure a container to work with a site that uses multiple domains. Other than that they work together fine. I would also recommend the Cookie Quick Manager extension, which lets you manage cookies on a per-container basis. If you have been using Multi-Account Containers by it self, then any links you open from a page will open in the same container (say reading news sites from HN), and you likely have a bunch of cross-site cookies stored there. This extension will let you clear out any undesired third-party cookies that have gathered in the container. The UI is a bit unclear at first (which of these three trashcan icons scattered across the page delete the subset of cookies I want), so read the tooltips before clicking an icon.

pavon 4y ago

I use and love this extension. The main complication that would prevent it from being a mainstream solution to cookie clearing is automating the decision of when to create a new container vs continue to use the existing one when links are clicked. Going by domain name (using Public Suffix List) breaks a lot of SSO implementations, and the occasional payment processor/verification flow, and other situations that redirect to another site, but pass information (or save state to have on return) via cookies.