Thanks! Merci !

Getting there, but could definitely use regexes. Possibly adding containers as well instead of the need to do so in preferences.

Thanks for the addon :)

Pardon, can this addon work with the whole URL provided? For example, I am specifying a certain Google spreadsheet in Containerise settings, with the whole document ID, but the expected result does not seem to appear, that spreadsheet is still being opened in the default container.

multi-account containers is too limited for me.

This add-on is getting there but needs regex support so that I can direct www.google.(co.uk|com) and others to a "tracking" container and console.cloud.google.com to a "company" container (because they use two different google accounts).

Other people have mentioned wildcards, but that's going to be difficult to code effectively - regex will be a better option.

To dev: "cookie autodelete" addon makes a great working model of how to demonstrate regex and wildcards effectively to the uninitiated.

Essenial addon for using containers, love it!

Thank you. The only one that works for me.

Good job!

Simple and functional, love it!

Suggestion:
* autofill with current URL when adding a new rule
* move save button below rules fields

Excellent, could use some work on the design side, but it functions perfectly.

The add-on seems very promising, but doesn't seem to work with Conex, I use intensively.
Can the 2 be made compatible ? or even merged, if I dare to suggest ?
They should be really complementary.
Have nice day!

This is a great start - but it needs works:
- Sync my settings between Firefox installs.
- Set a default container

Otherwise it works really well.

Just what I want.
A little problem, I'm not sure whether I can use wildcard or regex in the domain list, hope can add instructions about it.

Feature Request: hope can add a option, let opening new tab without container for unmatched domain, cause for my case it's almost unnecessary, though maybe the default behavior is useful for somebody.

Great use! But as someone suggested, I wish there is a default/fallback option where any website not matching any domain would be opened in a default container.

love it, but i wish it would open all websites by default in containers or at least to have an option to toggle on this behavior.

Works well. This seems great if you're using containers as a way to keep certain websites and account info quarantined in a container where it can't be read by other sites. Support for containerising based on regex pattern matching might be a good advanced feature.