6 ms·
I'm using it since it was launched. For my use case, it lacked the ability to use a different container for a page based on the entire URL, not just the domain.
by nikeee 4y ago
I'm using it since it was launched. For my use case, it lacked the ability to use a different container for a page based on the entire URL, not just the domain. For example, I've certain GitHub orgs that I'm using a separate account for. So the built-in ability to open sites based on the domain does not work for me.
I found the extension containerise [1], which offers the ability to assign containers based on globbing and/or a regex pattern. It's not something a typical "normal" user would need, so it's reasonable to not include this kind of feature in the built-in account container implementation.
[1]: https://addons.mozilla.org/en-US/firefox/addon/containerise/ https://addons.mozilla.org/en-US/firefox/addon/containerise/