3 ms·
There are other use cases for containers besides third party cookie isolation. If you want to have two separate sessions for a site, you'd still need containers
by gruez 6y ago
There are other use cases for containers besides third party cookie isolation. If you want to have two separate sessions for a site, you'd still need containers.
- als0 6y agoPrivate windows can let you do that, so you don't really need containers.
- daveFNbuck 6y agoHaving containers means you don't have to log in every time, and you can have multiple sessions open in different tabs in the same window.
- magicalhippo 6y agoI have multiple sites like Github, Dropbox etc where I have multiple accounts I'd like to access separately. Typically private account vs work account, but also other scenarios. Containers makes this a breeze. In addition, at least Firefox only has a single private session. So if I open a site in one private window and another in a different one, they're in the same session, sharing cookies etc. Not so with different containers.
- happymellon 6y agoI find this a horrible usecase for me, I keep my password managers separate from my work provided one and my personal one. Containers don't solve this, and I use profiles, which I have to be thankful for MultiFirefox for fixing it. But only on MacOS. I don't understand why fixing profiles isn't a priority, I find the usecase for them is completely different to containers which are awesome in a completely different way.