Comment by btreecat
3 years ago
I understand your dislike of the default workflow for Firefox profiles. Fortunately you can launch them from the CLI, so I usually creat an alias to my alt profiles then launch the browser from the shell.
3 years ago
I understand your dislike of the default workflow for Firefox profiles. Fortunately you can launch them from the CLI, so I usually creat an alias to my alt profiles then launch the browser from the shell.
Also Firefox Multi-Account Containers do things that Chrome profiles can't do at all.
the opposite is true, too, since "Clear History" in Chrome Profiles behaves correctly and (AFAIK) is scoped just to that Profile unlike our container friend: https://github.com/mozilla/multi-account-containers/issues/3...
I still use them because combined with https://addons.mozilla.org/en-US/firefox/addon/open-url-in-c... ( https://github.com/honsiorovskyi/open-url-in-container ) is a game changer for my workflow but it does make me sad that issue has been open for so long
To my understanding: the built-in "Junk" container auto-clears history, as well as "In Private" boundaries apply per usual for any container you open "In Private". Containers that I truly need to regularly clear history on, divorced from the rest of my Profile go into their own Firefox Profile. MAC is on top of/in addition to Firefox Profiles.
Multi-Account Container nicely reduces the need to juggle different Firefox Profiles, but it doesn't eliminate it. (I certainly still use a mixture of both for a myriad of reasons.)
If something requires CLI to work in a reasonable way it is a failure.