Oh wow. I used containers for a while, but the official plugin for managing them was awful. You had to go to the site, set the container, then click an approve button the _next_ time you went to it. Took forever to get things set up, and it never synced the settings despite claiming it would. I'm going to give this one a try. Thanks!

> but the official plugin for managing them was awful

I wish we'd stop being so hard on products. It's likely those developers read these comments. Having babies be called ugly by your peers is rough, actively trying to be more respectful on the internet leads to a nicer industry.

EDIT: Just to clarify - I'm not saying your intention was disrespectful. I've written many comments similar to this, and continue to do so, but I've started to try and curb it because I imagine it's what YouTubers feel like reading their comments section.. But this is by our own peers in our industry.

They should not take it personally. The UX/dev people at Firefox should take that as a constructive criticism.

Since when is constructive criticism expressed in words like “awful”?

You should take be asking the question why are the users using words like "awful"

I was quite frustrated by this as well, but then I remembered that the design goal of the extension is allowing logging into the same service with multiple accounts, not isolating services from each other. That is why the secondary functionality, the possibility of isolating tech fiefdoms, is less polished. It's not the main show, it's just a happy side effect.

Containerise and Cookie Autodelete together are indeed a very good addition to uBlock and uMatrix, and if you already have some Regular Expression classification rules written for Cookie Autodelete, setting up Containerise is very quick. It works like a charm even with the Firefox Multi Account Containers extension itself disabled.

Thank you thank you for posting this!

While I do agree with some reply-ers that @pkulak's critical wording was a bit strong in the sibling comment here, I have been incredibly frustrated with the default "Multi-Account Containers" add-on.

They have a facility to delete domains from a container, but no facility to add one: something I would've thought would be one of the first things one would want to implement. I understand resources are not always plentiful, but they've added a bunch of other features and yet this one is still lacking.

This is especially infuriating for "intermediate" domains forming parts of a redirect (Google have changed their subdomain structure recently and placing different Google properties into separate containers is now impossible with Multi-Account Containers due to their redirect structure)

The pattern-matching feature in `containerise` looks even better again.

Hoping it works as well as it looks; going to give it a try now.

This add-on has the same problem as Temporary containers. If you want to isolate Facebook and click a link to Spotify it will open Spotify in the Facebook container :(

So far only the Google/FB container add-ons do this right.

If I understand what you want correctly: the Firefox multi account container extension (is that the default one?) allows to "manage containers" and by clicking on the one you want you can select "limit to designated sites" so you can, from a container, click a non containerized link and get that link opened in the default/different container

Thank you thank you! That's fantastic! I wish I didn't have to manually assign containers but ya know what, good enough.

In temporary containers you can set up what should happen on different actions (left click, ctrl+click, etc) and different domains.

https://github.com/stoically/temporary-containers/wiki/Globa...

> If you want to isolate Facebook and click a link to Spotify it will open Spotify in the Facebook container :(

If you are talking about the Temporary containers extension, that's not the case. The extension is not the most easy to use, but it certainly supports opening Spotify in a different container when clicking a link in FB. You either don't have the Navigation→Target Domain set to Different from Tab Domain & Subdomains or you have Exclusion Patterns set which exempt Spotify.

Just enable "Default container" in its settings to isolate everything. (For advanced usage, also see the help button)

Right-click the link and click "Open in new container tab > " and click the container you want.