6 ms·
I wish every domain could automatically be opened in an individual container. I don't even need to know about them.
by IanSanders 7y ago
I wish every domain could automatically be opened in an individual container. I don't even need to know about them.
- matsemann 7y agoThat would break a lot of stuff, though. And then I don't just mean "bad" tracking, but normal auth flows etc
- katet 7y agoYou're quite right - I have some trouble with "modal" popup windows and the Atlassian Single Sign On in particular with the temporary extensions tab. But I eventually figured out to copy and paste those URLs and manually whitelist them to a specific container tab I wouldn't recommend it for family or friends, but I'm happy with the trade off
- pyr0hu 7y agoThere is a temp container extension that does exactly this.
- katet 7y agoAsk and ye shall receive: https://addons.mozilla.org/en-US/firefox/addon/temporary-containers https://addons.mozilla.org/en-US/firefox/addon/temporary-con... I use this in combination with "normal" containers and it works a treat
- SAI_Peregrinus 7y agoSame. The mix is IMO the best way to get privacy while keeping usability. It obsoletes things like cookie auto-delete. There is some annoying UI lag when opening a new tab though, as it takes a fraction of a second to swap from default to a new temporary container.
- xenophonf 7y agoI use this plus Containerise, but with recent updates to Temporary Containers, I don't think I need Containerise any more.
- Yhippa 7y agoJust curious: is there significant overhead to running each domain in it's own container?
- markosaric 7y agoThere's also the privacy.firstparty.isolate in about:config which isolates each site.
- 0-_-0 7y agoThat's an existing Firefox feature called First Party Isolation. Here's a plugin that toggles it: https://github.com/mozfreddyb/webext-firstpartyisolation https://github.com/mozfreddyb/webext-firstpartyisolation It sometimes (rarely) breaks payment processors but otherwise works fine