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.
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
... and then you have a fresh session context that doesn't share cookies with the others so you can log into services as different users. As a developer this is very handy for testing multi-user workflows, and had numerous uses as a more general user too, and it was easy to do ad-hoc without needing to setup multiple profiles first.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!
[0] https://github.com/mozilla/multi-account-containers/issues/4...