[pingec]

Slightly offtopic but I think the problem of rogue addons applies to firefox as well. I wish it were possible in firefox to limit which addons can be loaded on a per-container basis. The extensions I want loaded on banking websites, social media and youtube are completely different. And limiting them per-container makes it a relatively simple mental model to reason about.

[ajdude]

I was just thinking about this the other day. I would love to keep google/gststic blocked in noscript on most containers except the Google container.

[njsubedi]

In that case you can use multiple profiles.

[pingec]

I was able to learn how to use containers quite quickly and some container addons make it very easy to use them. Not so much for profiles, setting up multiple profiles seems very tiresome and honestly whenever I look up how to create multiple profiles I lose interest. Would really love a solution that is as easy to manage and use as containers and allows to control which addons are allowed to load/run.

Edit: Also IIRC multiple profiles cannot be synced across devices through the same firefox account while it is possible with containers

[Kye]

The point of containers is to not have to juggle a bunch of profiles.

[capableweb]

Hm, not really, they have different use cases, and Containers was never meant to 100% replace Profiles.

Containers are for being able to keep separate identities in the same browser window, but on a per-tab basis.

Profiles are for being able to separate different browser instances, with all their settings, extensions and so on.

While Profiles was used before to do the same thing that Containers now allow you to do, there are things you cannot do with Containers that you'll need to use Profiles for. Having separate extensions for different sessions is one of those things.