Hacker News Reader

The Firefox "containers" experiment (available in Nightly at least, maybe earlier) lets you set a site to always open in a certain profile. Even if you use ctrl-T (or ctrl-click on a link from a default tab, etc.) to open a new tab in Default, navigating to a site that's set to always open in container B will cause that tab to switch to container B.

I put this thing together a while back to help out with accidentally opening things in the wrong tab. You can right-click on a tab and 'move' it to a different context. It's a bit of a hack, in that it destroys the old tab and replaces it with a new one, but it's still quite useful.

https://addons.mozilla.org/en-US/firefox/addon/context-plus/

We love getting issues on our GitHub repo:

https://github.com/mozilla/testpilot-containers

And we're asking folks to upvote their favorite issues, so we can point more add-on developers at these lists. Since we can't solve for every workflow and use-case, we really want to enable an ecosystem of container-aware addons. (Some of the other comments here link to the already-growing number of container-aware addons)

And check out https://developer.mozilla.org/Add-ons/WebExtensions/API/cont... if you're interested in making your own.

> I see on their little drawings they show some cool drop down under the + button at the right of the tab row, but I can't find any such functionality.

Click and hold the new tab button. You should see the menu.

> Missing: easy way to open a new tab in a specific profile

Long click the new tab button then select the profile. Or just click the button on the toolbar and select the profile.

> Missing: a way to fix certain hosts to certain profiles.

When you click the toolbar button, you get the option to always open in the current container.

> Long click the new tab button then select the profile. Or just click the button on the toolbar and select the profile.

Further to this, I've been using (and meaning to embellish on) a little trick to make this even simpler, without having to use the mouse, using the "always open this host in container X" feature.

I have 2 gmail accounts so don't want to tie gmail.com to a specific container. I only have 1 pagerduty account so I have that open in my Work container automatically. So, to get to my work gmail I open a new tab (Ctrl+T), go to pagerduty (you don't have to wait for it to load), then go to gmail. Voila, work gmail without the mouse.

The embellishment is to set up work.mydomain.com, play.mydomain.com, whatever.mydomain.com. Tie each of them to a container and go from there.

> Missing: a way to disallow any non-whitelisted hosts from a tab. E.g. having a gmail tab is useless, because every link you click will open in that profile (and you won't notice because hey, it works) and now your gmail credentials and cookies are available there. Again defeats the purpose. Especially for a "Banking" tab, for example.

You can mitigate some of this with Cookie AutoDelete which has support for contextual identities. After you close a tab it'll nuke cookies for any non-whitelisted domain for that context.

But at that point the third party website might have already accessed those cookies.

I think parent comment wanted something more like First-Party Isolation (privacy.firstparty.isolate and privacy.firstparty.isolate.restrict_opener_access in about:config, use with caution - it will break things, including breaking Cookie Auto-Delete extension)

https://www.reddit.com/r/firefox/comments/6y7lpw/what_is_fir... (sorry, don't know any mozilla.org link for FPI that has any good description what it does and how it works)

> Missing: segmentation of plugins!! Different NoScript or µblock settings per profile? yes please! Or even just native Firefox settings (3rd party cookies, clearing policy, etc) per website per profile would be lovely.

Privacy extensions could do this on their own. They can integrate with containers where it makes sense. Enforcing it from the firefox side would probably be more confusing than useful.

> EDIT: Another missing: clear cookies only from a certain profile.

Extensions could implement this.

> Missing: a way to disallow any non-whitelisted hosts from a tab.

Extensions could implement this.

Fingerprinting may be a thing, but you can clearly see a big different in google results when you are logged in or not.