5 ms·

I love this feature, but it seems missing a critical thing. You can say 'always open websites A1, A2, A3 in container Y' but you can't say 'container Y only hos

I love this feature, but it seems missing a critical thing. You can say 'always open websites A1, A2, A3 in container Y' but you can't say 'container Y only hosts websites A1, A2, A3'. After time the container gets polluted with cookies from links clicked on website Ax. Hopefully this gets fixed soon. Edit: replaces 1 website with multiple websites Edit 2 : Another useful feature, would be cookie policy per container. So when I quit FF, I can delete all cookies except those in Container X

gavinpc 9y ago
Haven't used the feature, but can you whitelist cookies on a per-container basis? If so, then I'm in. If container Y is only going to open website X, then just block all other cookies.
- fish_fan 9y ago
  Yes, you can. The cookie settings are per-container (and there’s a surprising amount of customization per domain, though I wish it had decent wildcard support, it turns out to not be much of an issue).
  - diafygi 9y ago
    I think what parent meant was: if I use one container for webmail, can I set it to remember my webmail cookie, but not any cookies from links I open from my email? Is there now an option to whitelist specific origins, and block all other cookies by default?
    - fasquoika 9y ago
      It sounds like maybe you want privacy badger?
HanyouHottie 9y ago
I think this is the only sane way to deal with cookies: https://addons.mozilla.org/en-US/firefox/addon/cookie-autodelete/ https://addons.mozilla.org/en-US/firefox/addon/cookie-autode... (or Self Destructing Cookies before Firefox 57)
- drdaeman 9y ago
  AFAIK, C-AD has no support for DOM Storage or IndexedDB (or other legacy APIs if they're still alive, like Application Cache), though. I think it doesn't support Flash LSOs, too. It's very inferior to the SDC, and cannot be considered a reliable solution for sites to forget you. Not its fault, just that there are no APIs for this. Nor there's any protection against HSTS and HPKP pinning, ETags or other "supercookie"-grade stuff. I'm not sure even Contextual Identities are enough, given that e.g. HSTS leaks into incognito mode if the flag was already seen in non-incognito session. That's only a suspicion, though - I haven't checked it, and it's well possible containers are isolated.
thaumasiotes 9y ago
I want different settings for different containers. Sure, isolating cookies is helpful, but let me send them through different proxies too.
- jdalgetty 9y ago
  This is a key requirement to make this useful to the power user.
Vinnl 9y ago
Although I have no idea how an interface for something like this would look, it does sound like an excellent idea! Could you suggest it here if it has't been suggested yet? https://github.com/mozilla/multi-account-containers/issues https://github.com/mozilla/multi-account-containers/issues

gavinpc 9y ago

Haven't used the feature, but can you whitelist cookies on a per-container basis? If so, then I'm in. If container Y is only going to open website X, then just block all other cookies.

fish_fan 9y ago
Yes, you can. The cookie settings are per-container (and there’s a surprising amount of customization per domain, though I wish it had decent wildcard support, it turns out to not be much of an issue).
- diafygi 9y ago
  I think what parent meant was: if I use one container for webmail, can I set it to remember my webmail cookie, but not any cookies from links I open from my email? Is there now an option to whitelist specific origins, and block all other cookies by default?
  - fasquoika 9y ago
    It sounds like maybe you want privacy badger?

HanyouHottie 9y ago

I think this is the only sane way to deal with cookies: https://addons.mozilla.org/en-US/firefox/addon/cookie-autodelete/ https://addons.mozilla.org/en-US/firefox/addon/cookie-autode... (or Self Destructing Cookies before Firefox 57)

drdaeman 9y ago
AFAIK, C-AD has no support for DOM Storage or IndexedDB (or other legacy APIs if they're still alive, like Application Cache), though. I think it doesn't support Flash LSOs, too. It's very inferior to the SDC, and cannot be considered a reliable solution for sites to forget you. Not its fault, just that there are no APIs for this. Nor there's any protection against HSTS and HPKP pinning, ETags or other "supercookie"-grade stuff. I'm not sure even Contextual Identities are enough, given that e.g. HSTS leaks into incognito mode if the flag was already seen in non-incognito session. That's only a suspicion, though - I haven't checked it, and it's well possible containers are isolated.

thaumasiotes 9y ago

I want different settings for different containers. Sure, isolating cookies is helpful, but let me send them through different proxies too.

jdalgetty 9y ago
This is a key requirement to make this useful to the power user.

Vinnl 9y ago

Although I have no idea how an interface for something like this would look, it does sound like an excellent idea! Could you suggest it here if it has't been suggested yet? https://github.com/mozilla/multi-account-containers/issues https://github.com/mozilla/multi-account-containers/issues