They're quite practical even if you don't care about tracking. I have different containers for my work and personal Google accounts and they make things much easier than relying on Google's support for multiple accounts.

They're also great for development. I have different containers for each user I use while working on logged-in flows. I can just go from tab to tab to test different user experiences or switch between users in a multi-user interaction.

Totally share the love regarding container tabs.

I don't, however, like how the UI/UX is implemented. In particular, the management of containers -- why do I have to dig so deeply to add new containers? Also, as a color-blind person, the slightly colored thin bar above the tab is not a sufficient identifier. It just seems all sort of after-thoughty and jumbled to me.

Having said that, I converted to FF being my primary browser from being a long-time Chrome user and am happy about the change.

I wish the addon would sync its container configuration accross Firefox Sync. Setting my containers manually on the multiple computers I use daily is a real pain in the ass.

No, the best thing about Firefox is Tree Style Tabs https://addons.mozilla.org/en-US/firefox/addon/tree-style-ta...

The best thing about FF is about:config. It tunes in to the legacy of Netscape and Amiga where you could and can configure everything to how you like it. This is freedom, unlike chromium.

I tried to move from Chrome's profiles to Firefox's container tabs. I prefer Chrome's take on it where sessions are shared across all tabs in a window rather than across similarly styled tabs in the same window.

.. I just went to find the github issue for other people with a similar need[0] and found someone has posted a link to an extension called sticky containers. A new tab opens in the same container of the last one. It's actually pretty close to what I'm after..

https://addons.mozilla.org/en-US/firefox/addon/sticky-contai...

[0] https://github.com/mozilla/multi-account-containers/issues/3...

Containers are such a great idea.

My one wish is if you could set a default container. I use FF to browser Facebook primarily and want that to be default, but instead I have to load Firefox then load a container then load Facebook. Wish it were just open FF -> Facebook is homepage.

So at work we have a jenkins instance, which uses github (on prem) OAuth to sign in, and it logs you out after a very short period of inactivity. Except that jenkins or the way we have it configured or the way we have the reverse proxy in front of it configured is buggy, so sometimes when you try to log back in, you are just redirected to the front page, and you're still not logged in. To workaround this, I had to clean out my browser cache + cookies + other bits of history whenever this happened in order to log in.

Your comment just gave me the idea to: install the container tabs plugin, tell the plugin to always open our Jenkins site in the "Jenkins" container, and then when the bug happens, I can "clear cookies etc" on that container, without destroying my history and login sessions in the rest of my tabs.

After playing around with it for 5 minutes, it seems you can't clear cookies on a container basis. Also apparently only cookies are isolated, but other bits of history aren't. So this might not work. Alas. I almost found a solution. I did find that ctrl-shift-del opens a clear history popup though, instead of going through that wretched menu.

Container is great. I have to toot my own honk. The addon Session Boss supports container seamlessly. I have multiple GMail accounts that I put in different containers with their own logon and cookies. Session Boss saves the tabs and containers in a session and easily restore them the next time I need them.

Chrome has this too. I doubt its effectiveness as there are ways to fingerprint your browser without using cookies/sessions

This has been a first-class Chrome feature for years, for whatever it's worth.