Multi-Account Containers
support.mozilla.org
support.mozilla.org
Containers are still synced separately, so any fresh install of Firefox will have the tutorial UX and the default 4 containers, even after syncing.
Also, address bar completion is still monolithic, making it very easy to accidentally open a site in an undesired container. That can be worked around by adding every domain to a default container, but most of the utility of containers is to use several for a single domain, i.e. multiple email accounts each with their own container instances.
Containers are a feature I find very valuable, but they really need their UX to be a core browser feature, not an addon.
https://addons.mozilla.org/addon/containers-helper
The simplest improvement is that you can use e.g. Alt+Shift+D to open a little popup and start typing to find your container(s).
You can also use the extension to import and export containers, as well as some other features.
The extension respects your privacy completely and is not programmed to make any outbound network requests.
I don't know when it arrived, I'm pretty sure it hasn't been there too long, but I don't pay too much attention to this extension's UI. I'm running Firefox 109.
I install MAC despite my dislike for what the UI has become.
The UX was fine until Firefox started pushing its VPN service via this extension. I encourage the use of VPNs, that isn't my objection. But now the installation of MAC requires too many clicks just to configure it, and some of those clicks are to dismiss things that I didn't request.
Good UX practices:
1 = offer reasonable defaults
2 = be visually intelligible (make it easy to recognise borders, boxes, controls)
3 = make it easy to access important properties (don't bury or hide what people need)
4 = don't be annoying, nagging, exhausting, or confounding
5 = favour exposing features in an organised way
6 = let the user customise
The MAC extension suffers in points 2, 3, and 4 during installation. Now that Firefox has forced the grouping of all extensions in an Extension folder that cannot be moved, we now have a problem with point 6 too.https://addons.mozilla.org/en-US/firefox/addon/aws-sso-conta...
But completely agree, this should be a capability. It's like how Google Chrome profiles don't have the "open in another profile" menu option until you have two profiles already opened.
brilliant functionality, just the UI is beyond awful
1. Install Firefox.
2. Log in to fresh Firefox instance.
3. Let browser-wide sync happen.
4. Sync installs multi-account containers addon.
5. Four empty default containers are created. New user welcome flow is active.
6. Sign in to multi-account containers addon. Wait for container sync to do its thing.
7. Containers sync invisibly in the background.
- Default containers that you deleted before (in the instance you are syncing from) still exist in this fresh instance.
- New user welcome UX is still active.
So each time i setup a new browser and sync then, i have to go through and manually delete all the duplicates.
They dont re-appear once deleted and changes still sync (ie: if i add a URL rule to always open in x container) but holy crap is it annoying.
It also would never sync to my laptop for some reason?
The overall bad syncing experience was the main reason I stopped using them.
I dont setup a new machine all that often that I care too much. I figured it was a misconfigured cloud DB point, that at best I could get Mozilla to clean up and let me re-sync, but even then didnt bother to open a ticket.
Was expecting it under the standard account sync setting page.
I've been using a non add-on store addon for this.. and no idea why something basic like that would not be in the core or this add-on
https://addons.mozilla.org/en-GB/firefox/addon/containerise/
I'd have every tld on it's own profile and allow creating groups that merge profiles if needed.
It's a bit tedious to set it up at first but it's the only way I know of to get the following functionality:
With GMail open in a "google" container, non-google domain links open in non-google containers (configurable which container if any). Google domain links (drive, calendar, maps, etc) open in the google container.
Once setup, this means in your "standard" or non-specified container you can log out of all google services and stop their most explicit tracking of you through simple account cookies being read across the web while you search, etc. No longer when you visit sites that allow sign-in with google will your account name be auto-suggested, because the sites don't have that level of tracking info when you're browsing and searching outside of the google container. Viewing random trash yt videos will no longer sway the recs you get in yt.
The downside is that my google searches, done outside the google gulag, run into captcha prompts b/c I guess google search doesn't expect that much consistent traffic from someone who isn't signed into one of their services.
edit: this also means that you can, for example, containerize gmaps and set it up so that non-google domain links followed out of maps open in a non-google container. clicking a link to a business's website from their gmaps page no longers propagates your google account cookie to their site, etc. it opens in a different container, automatically.
But you just tell it not to open a temporary containers for that domain and you're good.
So really I've only seen this take much thought when combined with temporary containers.
1) i wish there was a way to automatically delete cookies/cache/history from specific containers every time. My personal container needs cookies and logins saved. My other containers don't need persistent cookies.
2) I've always wished for protonvpn to apply to only specific containers. Reading this now though, I see firefox's VPN does that so that's very cool, I might need to look into their vpn.
It will let you open containers that trash cookies on close. You can also set certain URL's to always open in a tmp container which is useful for sites that only let you read x amount of article per month.
[0] https://addons.mozilla.org/en-US/firefox/addon/auto-tab-disc...
My assumption up to then was that each newly opened Incognito tab or window was it's own private session, but this turned out to be wrong - they all share state, as if you had one separate but shared profile called Incognito. This was a little upsetting as I'd been using Incognito for years without realising the data sharing going on.
Temporary Containers does what I'd expected from Incognito. Each new temporary container has its own isolated cookies etc from all the others. So now I open a TC when I want to visit a site without identity or tracking, or to login temporarily with a different account, and don't use Incognito at all.
to provide context, i still use incognito, but i consider incognito mostly about hiding things from myself -- i use it almost exclusively for porn, because i don't want my porn habits in my browser suggestions. temporary tabs still land in the recent urls and such.
What I meant is if you open what you would otherwise open in an incognito window in a container instead, you can restart your browser without those tabs being closed and the respective state being lost.
https://github.com/mozilla/multi-account-containers/pull/249...
https://addons.mozilla.org/en-US/firefox/addon/cookie-autode...
Settings -> Extension Options -> Enable Support for Container Tabs
Gives a lot of flexibility, and I'm a lot less nervous opening stuff in 'temp' session when I know everything else is safely in totally different profiles/directories.
For #2 you do not need Firefox's VPN service. I am using it with wireguard and a socks5 proxy on the other end. I have a 'proxy' container configured but you can have more than one container with proxy as well. (In advanced proxy settings the syntax is socks://10.0.99.82:1080 )
Also, for some sites where I do "Sign in with Google", I like being able to 'stitch together' those session cookies by opening sites in the "Google" container so i can just waltz right into the "other site". On my other containers, they don't have the session cookie for Google in the background so I'm good. I use this for work-related things with SSO. Instead of naming the "static containers" "Work, Play, etc", I just call them the SSO-provider, and I know if I move an existing container into that or open a new tab using that container it will have the login I need.
My default settings are pretty locked down. Umatrix blocks a lot in my new temporary containers, and then I gradually unblock things.
Of course ideally I could specify specific extensions to work globally vs per profile.
(I'm perfectly fine having different profiles use different windows)
Even now, working at a single company, I use multi-account containers to keep tabs open for our different AWS and Datadog accounts.
Chrome has a version of this that doesn't work properly (much like "Incognito" mode doesn't work properly). This should be one of the biggest selling points of FF.
[0]: https://addons.mozilla.org/en-US/firefox/addon/simple-tab-gr...
I can only hope/assume they've gotten better since then - but it burned me really, really bad. So much that it still pisses me off talking about it all these years later.
Two of the original features that were extremely buggy were a hotkey to open up a visual overview of tab groups (originally Ctrl+Shift+E) and a way to search for a tab and reduce the number of visible tab groups to only groups containing a tab matching that search.
I see in the screenshots that this functionality seems to exist but also (based on the color coding) plays nicely with containers now. Would you be willing to vouch that it is more stable nowadays? Because if it isn't a steaming pile of shit that crashes if you so much as look in its direction that would certainly motivate me to return back to Firefox.
This hasn't happened to me -- my biggest issues have been around mistakenly clicking into a browser group in a second browser window.
Since I have two browsers open, I keep one for sort of ephemeral stuff which isn't on a browser group at all, then main stuff (email, slack, etc) on the one. Note that pinned tabs also work fine -- I have a pinned tab that's not in a container at all (my personal email) and it's fine across all groups.
If it helps, the extension now takes copious backups across browser upgradest at the very least (that I have to delete from time to time), files named `STF-backups-FF-<FF version>`.
> I can only hope/assume they've gotten better since then - but it burned me really, really bad. So much that it still pisses me off talking about it all these years later.
> Two of the original features that were extremely buggy were a hotkey to open up a visual overview of tab groups (originally Ctrl+Shift+E) and a way to search for a tab and reduce the number of visible tab groups to only groups containing a tab matching that search.
Sorry to hear that... I have to say that I don't use the hotkeys that much -- I don't use a visual over view, I just go up to the add on, click it, switch into the workspace and usually I'm there for an 1-4 hours.
Maybe you could look through the release notes? I don't know what the version you used last was, but I defnitely haven't lost tabs or been very frustrated with STG in a long time.
The color coding is fantastic. I have most groups linked to a container profile, all new tabs open in the profile and everything is tidy, separate, and color coded.
I can definitely vouch that it's more stable these days -- I am daily driving it and haven't thought about it in what has to be months to years. It's a crucial part of my workflow -- I use it to seriously separate work that I do for various projects (of course I have to re-login to Github, Gitlab, etc).
The release notes honestly weren't all that helpful - but looking over the Git repo, it looks like a lot of the major crashing/session restoration bugs were squashed in 2020-2021 and the backup functionality was improved enough to make backups more user friendly and somewhat more automated (aka: worth using and not 4 days out of date). There are still some flaws but those flaws come from the extension suffering the limitations of being a web extension - which is a tangentially related but another huge gripe of mine.
Now if only I could find a way to restore my context-menu tab switching - a feature lost when FireGestures was killed off. I didn't use any of the other gesture functionality at all - I only used the "[Popup] List All Tabs" feature which worked great with tab groups back in the day. (See: "Wheel Gestures" http://www.xuldev.org/firegestures/features.php)
E: (moments before I was about to post...)
Holy. Shit. Gesturefy recreated that functionality - and around the time I had given up on FF too. Back to Firefox I go! I had tried Foxy Gestures thinking it was the successor to FireGestures but I never gave Gesturefy a chance back then. In case I was bad at describing it, you can test it out yourself after setting it up in the settings: "[Popup] All Tabs" as a wheel gesture - it is an absolute game changer and I am SO GLAD I can go back to my circa-2013~2016 workflow after all these years. Only downside is continuing to scroll doesn't highlight tabs to change - so a small step back - wonder if it is even possible with how WE's are limited.
The hobbling of web extensions seems only set to continue but really glad that super useful stuff can still be done with them (and hopefully that continues, or the browser fracturing intensifies).
For this reason alone, tab groups should be baked in imo
https://addons.mozilla.org/en-US/firefox/addon/simple-tab-gr...
I use them both together and it's amazing.
I use a combination of both every day at work.
I like chrome for some things too because you can make a single-site-browser window in chrome, so certain websites can be treated like first class applications in the alt tab menu.
yes absolutely.
I did this for my local jupyter notebook server and pinned it to my taskbar. effectively works like a desktop app.
The amount of storage that these chrome profiles occupy on the hard disk is sometimes irksome. I have not compared it to Firefox though.
https://addons.mozilla.org/en-US/firefox/addon/aws-sso-conta...
I dislike certain aspects of Brave for other reasons, but this is why I have an unholy number of browsers installed and end up making use of nearly all of them regularly, unfortunately.
It's not perfect, and I prefer Firefox's rules-driven containers, but for anything which requires Chrome I've found it sufficient.
[1]: https://arc.net/
This landing page has some screenshots at least https://students.arc.net/
An example of it being useful for work: I can have several AWS consoles for different environments open, so I can quickly compare configs between environments.
For personal use, I can contain facebook inside its own container so it’s cookies don’t pollute my regular browsing
E.g. Slack (work) => Twitter (social media) => ~~broken~~ as the redirect doesn't go back to the (work) container.
I can't think of a fix because any there is would break the privacy of containers.
The UX for default containers could really benefit from some kind of context-awareness, but I'm not sure what that would look like.
I'm thinking an intermediary tab that gives you a list of default containers (instead of only a single option or none at all) to choose from when opening a domain. Then, maybe, you could set a default choice based on the originating container. Or maybe a tree of sub-containers... This is where addon-defined UX makes sense.
In some cases though I do have to switch my default browser to Chrome, log in, then switch it back.
It works on Firefox mobile beta and nightly with an addons collection: https://www.ghacks.net/2022/10/20/firefox-beta-for-android-n...
Briefly, the core of the hack was this:
(1) Firefox network hooks were not linked to UI tabs.
(2) So, I traverse all the object graph and find indirect links.
(3) I used those links to connect the network hooks with the UI, even when they conceptually were independent from the FF extension.
I sent the extension to the "Extend Firefox Prize" but didn't came with a single mention.
I have 3 accounts on a website. I thought I could setup 3 different containers, one for each account. But it turns out that switching between containers is not simple. Whenever I tried to switch, I got a pop up from Firefox asking me if I was really sure I wanted to switch my default container for that website. Sometimes it sent me into a redirect loop with the prompt also. I did some googling and found that the consensus was that containers simply aren’t meant to be used that way.
Firefox Multi Account Containers seem to assume you will always use one container for one website, and you can’t easily use multiple containers for a single site. Or at least, it’s very inconvenient to do so.
I agree that the UX is horrendous. Most of that is a byproduct of implementing it as an addon instead of a feature.
I use MACs with a bunch of different AWS accounts for work, and the only papercut is having to right-click my bookmarks and choosing which container to open the console in (as opposed to having MACs integrated with bookmarks themselves)
I for instance have a bookmark for a page. I right click it and select which container to opening it in. I often open it in different containers, have different tabs of it open at the same time etc.
Love Firefox, and I like what the Multi-Account Containers are trying to be, but it just didn't work for me. And it sounds like I'm not the only one who's run into this issue.
I also uninstalled the extension after fumbling around with it for 5-10 minutes and not being able to open multiple containers of github without it forgetting what I just tried to setup or constantly bugging me about switching the default container.
It's dangerous to use a system that can't keep sessions independent. There are bugs that may cause you to inadvertently take action in the wrong account. I nearly botched one of our own accounts.
For example, Facebook is notorious for reading third-party site cookies and vice-versa. A collection of associations (X Facebook user visited Y sites) is then sold as a portfolio for targeted advertising.
I agree this isn't the feature that provides the most utility; it's simply the one that was originally at the front of the devs' minds.
The container setup/management UI is glitchy and it often forgets! containers that were created. It feels like a hack week project that got shipped to production.
Despite having containers, Firefox sometimes wants to open the managed website in your current window. Or doesn't ask you at all when you have multiple containers for the same site.
There's a lack of distinction between containerized / non-containerized windows. The colored tabs do not work or break down, leaving you in a mysterious or even dangerous state.
The integration with password management tools is obviously rough. But coupled with the browser's own attempts at session management, plus containers, it's a UX nightmare to log into the right container.
The last time I checked this out was last year. Maybe it's better now? Given Mozilla staffing, though, I'd guess not.
I really want this to work, but the current solution is worse than none at all. I've made do with keeping multiple browsers for different tasks.
Be careful if you use this. It breaks unexpectedly and that can lead to the wrong actions being taken in the wrong accounts.
Because syncing is a separate step - yet it still happens concurrently/unpredictably in the background - there is no avoiding the default new user flow that creates 4 default containers at install.
As it stands, Firefox containers are 10x more complicated than regular browsing and it exposes sharp edges.
been running it for years, never once has it forgot containers...
>>Firefox sometimes wants to open the managed website in your current window. Or doesn't ask you at all when you have multiple containers for the same site.
ok, so you right click and have it reopen in the correct container, not a big deal. Though I cant say I have ever had this problem either despite using it very day all day, 16 hrs + per say with lots of containers and tabs (often over 100 tabs open)
>>The integration with password management tools is obviously rough.
I use bitwarden, have no issue using it inside of various containers
Does containers also allow multiple winddows to share a profile?
For example, I have a work profile, and a home profile - and each has a window for browsing (eg: hn), and a window on my laptop screen for videochat (so when I look at the chat, I don't look way above the camera - which happen if I look at my main screen).
I can move tabs between these windows too (eg: quickly read something while still "looking" at the camera).
Does containers also allow this "single container, multiple windows" use-case?
I mean, I appreciate keeping a single window dedicated to my Work container running all of my work tabs to properly isolate my sessions, but sometimes I have services that I have to login on other profiles (e.g., I use a consultant Miro account that I DO want to run on the same window, even if it's not using my Work container).
It's also a lot easier to identify which tabs are running which containers thanks to their colored tab markers and the container name indicated on the address bar. It's essential if you have to say, login to two separate Gmail sessions on the same window without their sessions getting mixed up.
Finally, it's different from profiles because you can optionally associate websites to containers (e.g., if I open ycombinator.com it's opened using my Personal container while opening miro.com automatically loads a different container, while I disable this feature for sites that I login across multiple containers for different contexts, such as Gmail or the AWS Console)
Only hassle I have is that I sometimes have to disable the google one if a site requires google auth but is in a non google container. Redirection wont work otherwise. Only temporarily until auth has finished.
Also I like the integration with Mozilla VPN per container. But I wish they would support disabling the VPN for some or in reverse only enable tunneling for some containers. There was a an open issue for that. [2]
[1] https://addons.mozilla.org/en-US/firefox/addon/temporary-con...
[2] https://github.com/mozilla/multi-account-containers/issues/2...
If your company uses gmail, or any other single sign on, its a really good tool for separating work/home digital life.
multiple accounts for the same site
Facebook/instagram/reddit/youtube is really hard to have separate non-linked logins. Plus its a massive faff logging in and out. assigning accounts to tabs saves time.
keeping your youtube recommendations clear
Youtube's recommendation algorithm looks at all you are playing and figures out what you should watch next. If you see something music based, then it will hard pivot your recommendations to music. If you have something populist, then expect a fucktonne of clickbait.
Have a "clean" and "dirty" profile really improves the quality of the videos I get shown.
https://addons.mozilla.org/en-US/firefox/addon/open-url-in-c...
This extension gives the ability to create bookmarks that open in a specific container automatically.
When dealing with AWS accounts that are configured to use SSO. I’ll have to use IdP to login into awsapps.com. Then I have to choose AWS account and then click a Role that I would like to use for session. This is troublesome and breaks my flow. I wanted a way to quickly jump into a specific account without thinking too much.
For each AWS account that I need to use, I’ve copied a link from awsapps.com pointing at specific permissions set. When opening this link I will be taken to a specific AWS account, and if the session is expired it will prompt for IdP login and proceed to AWS account. Next, I’ve created a bookmark and crafted a url that uses the mentioned extension. It will open link in to a “staging” account in Firefox container company-staging.
Amazing feature, underrated.
This is what it was like a while ago though, I haven't tested it recently because I haven't had a need to log in to other tenants anymore since I moved jobs.
Also, it seems like it's been abandoned, since it has changed little since the introduction.
Here are some thoughtful 1 star reviews:
https://addons.mozilla.org/en-US/firefox/addon/multi-account...
https://addons.mozilla.org/en-US/firefox/addon/multi-account...
https://addons.mozilla.org/en-US/firefox/addon/multi-account...
https://addons.mozilla.org/en-US/firefox/addon/multi-account...
https://addons.mozilla.org/en-US/firefox/addon/multi-account...
https://addons.mozilla.org/en-US/firefox/addon/multi-account...
Honestly, my own testing and all these complaints and that it hasn't been given simple care and feeding mean I'm going to avoid it until all this changes.
It stubbornly tries to open both Gmail and Youtube in Google container. Even if I remove that container and create separate ones for Gmail and Youtube, when I try to open those sites in their respective containers, it will refuse to open it. If I restart firefox and retry, it goes back to creating the Google container and open both in that container.
Absolutely terrible UX for something that could be as simple as:
1. Right click on a tab and let me select a container
2. Ask if I want to remember it.
3. Actually remember it.
It actually shows the container in the address-bar which is a perfect spot for me to click on that and change it to another container - but noooo, that would be so obvious hence clicking on it does nothing. Great UX.
Everytime I want to support Firefox and come back to it, shit like this just drives me mad and makes me go to the terrible but polished alternative of Chrome. Sigh.
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/
- auto containerization based on url match
- keyboard driven way to open new pages in a specific container
FF transforms into a powerful browser OS running applications with hard boundaries.
The only UX issue (which admittedly could be because I have changed the theme to be minimal by hacking userChrome) is that sometimes the temporary containers I spawn are the ones I need to retain (user storage) etc and I tend to forget that and loose data.
[1]: https://addons.mozilla.org/en-US/firefox/addon/temporary-con...
But the primary usecase for me is to access a rarely used account temporarily without having to logout and login from the main account (AWS, Cloudflare, Google, etc).
Firefox, FireFox Nightly. It takes little time for you to understand the context(you see the icon or browser and know exactly what "profile" it is), there's no suggestion or link interference etc.
Would multi-account containers be better for that workflow?
I had about 6 or 7 Firefox profiles encompassing 2 of my businesses, clients, and some administration of my fiancée's companies she runs.
For each of my two businesses I had two separate profiles, one with personal accounts and a second I logged in with 'Admin' accounts for various services and infrastructure.
It was a little tedious, but it worked. However I would waste so much time tabbing through multiple Firefox windows working out what was the correct one for the job in hand.
Firefox Multi-Account containers got that down to two profiles, and I'd say I really only work 99% of the time in a single profile.
Simple Tab Groups is invaluable too to reduce the tab 'clutter' that comes from working out of a single profile/window.
Lastly as an added bonus, when I was comfortable with Multi-Account Containers, I successfully weened my fiancée off of Chrome and onto Firefox so she could flick between different accounts for those businesses she works with too.
I basically have different applications of chrome, each with a different profile. They wacht have a different app icon, browser color, and extensions.
It helps me focus a lot to have a different application (cmd-tab entry) for dev, media, general browsing.
Social media and other time traps are blocked on my general and dev browser.
Works very well I have to say. It copies Chrome using clonefiles (CoW on apfs) to save space.
The only thing is that updating goes through the main browser (automatic updates are buggy in this case). And I have to codesign when there’s an update, but the scripts take care of that.
Miles better than juggling with other browsers or incognito mode.
Go visit youtube.com and anything loaded from that page is in the same container.
You'd have to log into each google property as the sites would be separated from one another, and there would probably be a need to merge these containers if say www.example.com and example.com are the same site (or automerge if there is a 302 redirect).
Did I miss something in the settings?
Clumsy UI. It's useful (I use it) but its just not as simple as it could be.
Auto assigning a URL to a container is complicated. Opening and re-opening a URL in a container is complicated. Saving container state so you can re-open the same things is .. (you guessed it) complicated.
1. Eternal Terminal does not support ssh_config ProxyCommand, so both tunnels must be TCP.
2. Cloudflare Tunnel TCP proxies through cloudflared running locally on the client. https://developers.cloudflare.com/cloudflare-one/application...
#~/.ssh/config
Host et.example.com
Hostname 127.0.0.1
Port 10022
cloudflared access tcp --hostname ssh.example.com --url localhost:10022 &
cloudflared access tcp --hostname et.example.com --url localhost:12022 &
et et.example.com:12022
The following command must be run once to authenticate: cloudflared tunnel loginits similar to opening the video in an incognito window but with a container it will remember whatever cookie settings you choose instead of asking you each time
How Firefox’s Total Cookie Protection and container extensions work together
https://addons.mozilla.org/blog/how-firefoxs-total-cookie-pr...
* SOCKS5 proxy per container setting.
* More custom icons and colors for container.
This extension handles it correctly: https://addons.mozilla.org/en-US/firefox/addon/container-pro...
Each account gets it's own slice, each tab gets it's own transient unit. You get nested cgroups and accounting for free. Eliminating the resource hog problem and prioritizing workloads.
I'd love if Firefox as a bare URL handler ASKED, with an out of any profile context dialog, WHICH profile and window to load a URL in.
so you can have a different IP address per tab?
I feel resentful that the Temporary Containers extension isn't available on mobile Firefox. To me it would be as if adblocking extensions wouldn't be available. It's one thing of many that seems really different about mobile Firefox, to a point where the cynical part of me feels like mobile Firefox is being obsequious to advertisers or something for some reason in a way desktop is not.
It's also useful because InPrivate windows share a cookie jar in Firefox.
Wow, should it be a bug? Im Safari user, have little FF experience.
Looking at the docs it appears that Safari gets around this by just having a separate jar per tab? On desktop at least, mobile appears to be shared.
None of these things offers a big advantage over using virtual desktops, for example, but it's good to have choices.
I literally want the _opposite_ of that. Chrome makes it so that a Window is specific to a profile. Makes it very simple to keep say Work and Home profiles separate, for example. Especially if you set color schemes for each window.
That's fine, but not everyone does. I think both are useful and would prefer a browser that can support both profiles and "containers.
- You can configure rules, so onlinebanking.example.com (or whatever) always open in a separate profile for security.
- Your history/bookmarks/extensions/settings/etc. are not separate per profile.
I want ONE window with all my tabs, in a vertical List (tree Style Tabs and/or Sideberry) which is another feature Chrome lacks completely, it implementation of Vertical Tabs is TERRIBLE
This opens a new window with that profile, but you can switch between each window at will.
The lack of discoverability of that "about:profiles" page is indeed a UX issue compared to chrome, but other that that it works pretty well.
For most use cases, I find the more lightweight multi-account-containers more useful though.
And you can edit the shortcut to ask you which profile you want to use when you start Firefox.