The setting "Replace tab insted of creating a new one" does NOT work -- even if checked, the extension still opens a current website in another separate tab when the user tries to open the tab in another container.
Please fix this feature. Thanks.

Leider funktioniert die Synchronisierung entweder überhaupt nicht (auf Gerät A hinzugefügte Container tauchen auf Gerät B gar nicht auf) oder Werte werden total falsch synchronisiert, wenn man ein neues Gerät hinzufügt (erstelle Listen auf Gerät A werden scheinbar mit Standardcontainer von neu hinzugefügtem Gerät B einfach wieder überschrieben). Dabei ist die Idee mit den Containern super. Schade, dass Mozilla hier scheinbar gar keinen Wert auf eine saubere Sync-Funktion legt (siehe vorige Bewertungen zu diesem Thema), so ist es wertlos für mich.

I have several google accounts for different situations. I use the container to watch different types of videos on youtube without ruining my algorithm. It's faster to use different containers than switching the accounts. I also standardised to open google maps only in a certain container that is different to my standard google account. Same goes for mail tabs, where I simultaneously keep multiple containers open

I've been using this for several years. Have lots of containers to separate types of accounts and activity. Have appreciated the ability to sync the config across devices. Really keeps the cross-talk and tracking down. Feel it greatly improves privacy.

Fucking amazing! Was able to completely neuter Reddit's tracking so hard the Admins didn't know what the fuck hit them or what to do about it!

Power to the users! If a site is giving you grief? Chuck 'em in a tiny little bubble and tell 'em to fuck off!

Love this addon - it has all the functions you need to ringfence correctly - isolated sites can click out and you'll have all your normal cookies back - but the isolated target is none the wiser.

No hard work - set and forget, and done.

It's this easy.

I'll be doing similar for other sites - Shopping, Social media, Youtube... You name it.

The click target for Container management could be a tad larger for repeatable precision, Otherwise works as described. Android Implementation is much appreciated.

I just love what this extension does, preventing cross-talk between activated Container tabs! There is one, rather large, caveat, however, in that when initially setting up a URL in a designated Container, it easily completed, and it looks like you're done! BUT... the next time you use that URL (say you Bookmarked it), you are presented with a Container verification screen, where you have to say, "Yes, I actually DO WANT to use the Container that I thought that I already HAD set up!" What this means is that once you setup a URL to a Container, you have to immediately TRY that URL (possibly Bookmarked) to answer that verification page. THEN...everything works as expected. I consider it an inconvenience, but once you are used to jumping thru the hoops, its 2nd nature. And that does not detract from the purpose or function of the extension!

Works well for my use (on a single machine). I haven't used the sync-option! Other reviews report it is buggy...

Ajuda muito quem precisa acessar vários de logins diferentes, mas a sincronia tem problemas.

It was miraculous to use, but Mozilla does not care to develop or run anything without illegal corporations telling them what to do. Who agrees? Is the Internet not a conspiracy?

Irresponsible to have this extension published and available with such dire bugs. Whatever you do, DO NOT turn on Sync for this extension. You'll end up wiping out your entire configuration, your containers, your site rules, everything.

Needed to have multiple Web Outlook email accounts open simultaneously. Worked great. If pinned the accounts came back up without logging in again if Firefox exited and restarted. Would be absolutely perfect for me if the accounts came back up after a Restart.

Doesn't work well containing Google, can't sign in on gemini.google.com

Guaranteed to silently drop containers in the middle of your workflow, with no github interest in even acknowledging the problem.