Live data from Hacker News

Firefox Containers Preview

blog.mozilla.org

71–80 of 136 posts

Re: Firefox Containers Preview

#73
post #61
post #33

Earlier quoted context omitted.

> site-specific container assignments This is (or was, before I switched to Vivaldi) the killer feature of Firefox containers for me. I could banish certain tracking-heavy sites to their own containers so that they could only track where I've been on their own properties and not across the whole web. (Without having to remember to switch to their containers beforehand.) So I guess if I go back to Firefox, I'll still…

For me, this is almost an anti-feature. I still use it for a few sites, but the real killer feature of containers is that it becomes a breeze to use the same service with different accounts & identities, without logging in and out, and no shared state. Pinning a site to a container breaks that.

> use the same service with different accounts & identities

Last week, I needed to do Google Takeout on a doz different user accounts (hours between request and availability). In a few seconds, I had a doz temp containers to keep the sessions alive and isolated, until the downloads showed up.

Re: Firefox Containers Preview

#75
post #13

Firefox's Multi-Account Containers changed the game for me back in 2018 or 2019, and is what got me to switch back to Firefox for 95% of my personal browser use. The "Always open {{domain}} in this container" and the ability to open a specific container with a keyboard shortcut seem like small things, but I can't imagine life without them anymore. I never understood why it was set off to the side in an (official, fir…

Yep, same here MAC + Temporary Containers extension is how web browsing should be handled by default imo No website deserves permanence of any data in my browser unless I so choose I haven't seen similar functionality in any of the new generation of browsers, nor any of the Firefox spinoffs as-yet

>I haven't seen similar functionality in any [other] browsers

Brave has been advertising their new containers but I haven't tried them yet. https://brave.com/blog/containers/

Given Google's hostility toward non-chromium browsers, it's on my check-it-out list

Re: Firefox Containers Preview

#76
post #9

I'm a little confused here, I've been using the containers feature already for years now on Firefox. And I have no add-on installed for it, it just works. So what is it that they're adding?

> So what is it that they're adding?

They enable it by default without having to go to about:config or install an extension that use the container capabilities.

You have probably done one or the other a long time ago without remembering it.

Re: Firefox Containers Preview

#77

Earlier quoted context omitted.

Yep, same here MAC + Temporary Containers extension is how web browsing should be handled by default imo No website deserves permanence of any data in my browser unless I so choose I haven't seen similar functionality in any of the new generation of browsers, nor any of the Firefox spinoffs as-yet

>I haven't seen similar functionality in any [other] browsers Brave has been advertising their new containers but I haven't tried them yet. https://brave.com/blog/containers/ Given Google's hostility toward non-chromium browsers, it's on my check-it-out list

Brave containers are great.

They also have vertical tabs built in which is my preferred tab layout and is missing from Chrome

Re: Firefox Containers Preview

#78

I’ve been using Firefox Containers for years through Mozilla’s Multi-Account Containers extension.[1] Now that container management is available directly in Firefox, I’d prefer to use the native implementation if possible. Mozilla notes that the extension still adds some functionality: > “Installing the Multi-Account Containers extension developed by Mozilla provides a few benefits on top of the native container func…

> 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.

Re: Firefox Containers Preview

#79
post #43

I'm curious about Mozilla's seeming shift in strategy (possibly it was awhile ago and I overlooked it): For a long time, with relatively limited (compared to Google and Apple) development resources, they focused on minimizing upkeep and technical debt. They added and maintained features appealing to the vast majority, the non-technical users, and left the rest to extensions. Now I'm seeing geek and power user favorit…

Partly they're just exposing existing features. Containers were part of the browser already, the UI just didn't show them by default.

I'm still waiting for them to add a UI option to enable the `privacy.resistFingerprinting` setting.

Post reply on HN