Essentially it allows you to put different tabs into different light-weight profiles, with their own session, cookies, and state. That means if you want to log into Facebook but don't want Facebook following you online, just give Facebook its own container.
Mozilla has anti-tracking already baked in, but Multi-Account Containers are a whole other level of isolation, but without sacrificing usability (like traditional multi-profile/multi-user browsing).
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.
File | New Session
It didn't work for apps that are sensitive to permanent cookies (and other client-side storage) instead if session level options of course, where multiple profiles does (as presumably does Firefoxes containers? - I don't know as I've not yet used them).
Containers keep the cookies and other data, yes, so you don't need to re-login every time you start the browser.
Yes, but you can have as many active sessions as you need instead of just two.
Incognito/InPrivate/whet-ever-other-browsers-call-the-feature tabs/windows share the same session so that gives you at most two active sessions: normal and incognito.
The "new session" option in IE can have many more. For a lot of workflows two is enough, but sometimes I want something like "a couple of distinct base users, a manager, and an admin" for testing more complex user workflows.
I use them so I can be logged in to multiple AWS accounts at the same time - works like a charm!
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.
It is actually easy... once you found the option: Long press the "+" / new tab button, and on the bottom of the container list is "manage containers".
Ce soir je me coucherai moins bête.
Really usefull trick but not very discoverable.
If you know about them, for example from reading the code, you can create them. So at present about:config is a strange sort of place with lots of knobs but not all of them.
- prefs that a developer was too lazy to add to the list of pref; or
- prefs that serve only during automated tests.
You could scan source code for `Services.prefs` and `nsIPreferenceService` if you really want to find them.
.. I just went to find the github issue for other people with a similar need 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..
Now you can have multiple windows, each window with its own profile and the profile determines everything, from the browser's history to the extensions installed.
Here is an article that talks through the steps (on windows but it's similar for others) https://www.howtogeek.com/209320/how-to-set-up-and-use-multi...
Before the Quantum release we had a pretty cool extension for managing profiles that is no longer available, sadly:
I hope it gets implemented again.
I now do the "about:profiles" thing I mentioned. I don't know why they aren't exposing Profiles in the UI in an intuitive manner, makes no sense. For my day to day use, I think Multi-Account Containers are better though.
I have two LastPass accounts. One for work and one for personal use and I cannot use both of them in Firefox
That is the only reason I am not switching
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.
Also with the standard container addon you can specify that sites always open only in your specified container, so you could just set Facebook to always open in its own container that way.
Eh, back to my former opinion - Containers are great, Containers UX needs work.
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.
It doesn't clear cache but it will automatically delete any cookies when you close a tab or when you change the domain. That might do what you need, when you use it in conjunction with Containers.
On Chrome, theres an option to list cookies for a site by clicking on that padlock to left of site url, so quicker way of clearing cookies for your Jenkins site. Maybe FF has similar setup.
Then hard refresh browser should clear cache I think (ctr/cmd + shift + r on any system or ctr + f5 on windows).
I can't switch to Chrome since I can't live without tree style tabs anymore. I've become dependent.
If you're okay with using chrome: create another profile and only use it for jenkins, in fact, set up a shortcut that opens it in app/kiosk mode and maybe see if there's a commandline flag to clear all history every time you open it, that way all you need to do is click the shortcut and everything else happens in the background and it doesn't affect the rest of your browsing exp.
Both additional profiles and incognito browsing open a different window, with its own settings.
Which may actually be what pushes me to FF. Not out of spite, just that I was counting on Chrome profiles for this purpose, but they've gotten a lot harder for me to use for that (and were never as good as FF's multi-container thing, it sounds like).
Chrome supports multiple profiles. Mozilla's Multi-Account Container tabs isn't multiple profits. It is multiple isolated containers running under the same profile, in the same browser window.
A closer analogy would be if Chrome allowed each tab to have its own profile, rather than each window, and for each one to be lighter weight than a full profile.
With Chrome, even if you manually sync your profiles and keep the same set of extensions installed in both profiles, it runs 2 processes of the same extension. Even when the second profile window is closed.
But for me the deal breaker was managing a separate set of bookmarks.
daveFNbuck writes :
“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.”
But from a privacy UX perspective, both Chrome and Firefox accommodate this use case gracefully.