[illusiveman]

I'm not sure why this is even on the front-page now, given that it's been released for many years already, but in any case, here's my two cents about this topic:

Containers are a misunderstood technology. People think about them as a privacy feature, but that's far from real. The only benefit of containers is the ability to have different sessions of the same service in the same windows/profile. That's it. A good use case is when you need to work with multiple AWS accounts.

Cross-site tracking is already enabled by default since... 2018? So, using containers as a way of dealing with cross-site tracking is utterly unnecessary.

[lopis]

It is a privacy feature, specially when paired with Cookie Auto Delete. I have CAD setup to always delete cookies when I close all tabs of a website. But I can add exceptions per website and per container. So I have a Google container that is the only place where I allow Google to leave cookies on my browser. I do the same for a several other websites. Sure, Google can always track you somehow, like IP address, but it's not as easy to track you around the Internet when you always use a fresh new session on each tab.

[illusiveman]

do you realize CAD is unnecessary because Firefox has site isolation for a few years already?

anyways, it's CAD the one providing you that sense of privacy, not the container.

[lopis]

I don't just want cookie isolation. I want cookie obliteration.

[_joel]

Well that's strange as I still get hits on the facebook containers block, to tell me it's blocking tracking.