| > Now that container management is available directly in Firefox, I’d prefer to use the native implementation if possible. It's been available for years in stable, including the management page on the settings, if you enable them in about:config (privacy.userContext.enabled and privacy.userContext.ui.enabled). Plenty of us have been using them for a long long time without extensions. Based on the list of features, the announcement appears to just be flipping those settings on by default. > Are the containers created by the extension already shared with Firefox’s native container manager, or is there some migration process? Can I safely uninstall the extension and keep my existing containers, names, colors, icons, cookies, and active sessions? Most likely those addons flipped at least the first setting and just used the native implementation with their own interface. After Quantum and Electrolysis, Firefox was a lot more locked down and addons couldn't do stuff like this on their own. There was a previous thread a few days ago where a bunch of us were confused because we had these enabled and didn't remember enabling it, and some replies suggested the addons flipped the about:config setting. Edit: I just found my old comment in this post, the old post I was referring to is this one. It's been resurfaced from 3 days ago. |
This would be my definition of not available as a native user-accessible feature versus what they are launching now.