I’ve been a user of profiles since Firefox was Netscape. It took me a minute to realize that the feature isn’t toggled on by default. There’s was no mention of the functionality the the 145 release notes. It can easily be switched on in about:config by toggling the key browser.profiles.enabled from false to true. This new profiles functionality seems to be separated from current profiles though. I was hoping that my existing profiles would just be there. It could be that’s coming and part of why the feature is currently toggled off by default. Will be interesting to see how this matures.
There’s was no mention of the functionality the the 145 release notes.
That’s because it was in the 144.0 release notes, but rolled out gradually.
I mean, Firefox has had profiles for years before chrome did. And then they had multi-account containers and chrome still doesn’t have those. And now they have a new distinct feature that they’ve given the same name of profiles that is just slightly different from the already existing profiles feature.
@tyler Thanks for the insights! Looks like the “marketing push” of profiles after the recent update has made some of us (finally) aware of that feature 😂
It’s kinda understandable, but you should reasonably assume that Firefox did it first and anything chrome does after the fact followed that, unless Google thinks it will help them keep a tighter grip on the market, like Manifest V3.
Whatever this is, it’s not even slightly new, I’ve been using separate FF profiles for many years. And TFA literally says “Chrome was first”. No it wasn’t!
@JubilantJaguar Thanks for the feedback. We have since adjusted the article to precise that “profiles” itself is nothing new in Firefox, but the recent banner push after the Firefox update has made more users aware of it.
Firefox support literally tells you to “create a new profile” for certain problems, and has suggested that for as long as it’s existed.
