The one problem I have with this is that I want `mail.example.com` to always open in my work container, but `mail.example.com` redirects to `mail.google.com` and the latter is what ends up being saved, so it's not possible to assign to different Gmail accounts to different containers. I wish I could edit the URLs for sites assigned to a given container.
An Update on Firefox Containers
31–40 of 107 posts
Re: An Update on Firefox Containers
#32They mentioned my main peeve about containers: IMO control-T should open a new tab in the current container rather than in the default container. They implied that this could be fixed in an extension and linked some extensions, but those extensions appear to do other things. Has anybody found an extension that changes the control-T behaviour? Thanks. Edit: They've totally got the default right. Pressing control-T fro…
One of the few things I like about Chrome more than Firefox is the way it handles "Personas", a similar feature. Selecting a new "persona" opens a new window, and pressing C+T opens a new tab.
The downside with chrome's implementation is that they are completely isolated instances of chrome - there's no easy way to hop between containers.
Being able to right-click on a link in your personal container and open it in your work container is pretty slick.
Re: An Update on Firefox Containers
#33These look really cool. I've had Self-Destructing Cookies (or Webextension equivalent) on Firefox for awhile now to try to combat this problem, but it is a bit annoying that if I inadvertently close HN's tab or navigate away from it because I followed a URL, I need to log back in. Containers might eventually give me enough segmentation that I can feel confident with staying logged into some stuff without being concer…
Why not whitelist hn?
Re: An Update on Firefox Containers
#34This pollutes the term container, which up to now they were assisted by kernel security features.
Kernel security feature pollutes the term container, which for ages has meant something that contains.
Anybody with context can trivially differentiate between the two...
Re: An Update on Firefox Containers
#35Does anyone have any advice on how best to use this? Is it really best to make all shopping websites open in the same containers? Any thoughts on what sites/kinds of sites should definitely be in their own containers. Any recommended categories besides the default container categories?
One thing I've found really really useful is handling multiple google users over multiple google sites.
I want youtube & google music to only use my personal account, so I never need to switch accounts, so google music and youtube open in their own container where only my personal account is logged in.
I want gmail and calendar to use my work account, so they open in the default container and automatically use my work google user.
I know that you can set your default google account by logging into it first, but I specifically don't want one default, I want different defaults for different google services, and that use case is handled beautifully by containers.
Re: An Update on Firefox Containers
#36Does anyone have any advice on how best to use this? Is it really best to make all shopping websites open in the same containers? Any thoughts on what sites/kinds of sites should definitely be in their own containers. Any recommended categories besides the default container categories?
I wonder about this as well. What are people finding is the best use of the default container - what opens as a new tab? Do you keep that your personal container, and opt-in to other containers like work, shopping, etc. Or do you use the default container as your most used type - perhaps work - and opt-in to personal/shopping containers as needed? Keep the default container blank and try to always open up a specific…
It's useful for handling sites with really long login flows, and multiple accounts, so I use them as the exception, rather than the rule.
Eg: AWS I have a work and personal account, and their login flow sucks, but the work and personal containers handle this situation easily.
Re: An Update on Firefox Containers
#37I love this feature, but it seems missing a critical thing. You can say 'always open websites A1, A2, A3 in container Y' but you can't say 'container Y only hosts websites A1, A2, A3'. After time the container gets polluted with cookies from links clicked on website Ax. Hopefully this gets fixed soon. Edit: replaces 1 website with multiple websites Edit 2 : Another useful feature, would be cookie policy per container…
I think this is the only sane way to deal with cookies: https://addons.mozilla.org/en-US/firefox/addon/cookie-autode... (or Self Destructing Cookies before Firefox 57)
AFAIK, C-AD has no support for DOM Storage or IndexedDB (or other legacy APIs if they're still alive, like Application Cache), though. I think it doesn't support Flash LSOs, too. It's very inferior to the SDC, and cannot be considered a reliable solution for sites to forget you. Not its fault, just that there are no APIs for this.
Nor there's any protection against HSTS and HPKP pinning, ETags or other "supercookie"-grade stuff. I'm not sure even Contextual Identities are enough, given that e.g. HSTS leaks into incognito mode if the flag was already seen in non-incognito session. That's only a suspicion, though - I haven't checked it, and it's well possible containers are isolated.
Re: An Update on Firefox Containers
#38Any reason why new tabs shouldn't create an entirely new, isolated container by default? And then allow the user to close tabs implicitly by performing a merge operation with some existing container (say, dragging with the mouse with a hotkey held down onto an existing tab group representing a single container)? And alternatively, "merging" with the empty container, which would retroactively implement incognito mode…
> Any reason why new tabs shouldn't create an entirely new, isolated container by default?
That sounds a lot close to self-destructing-cookies, or now, this:
https://addons.mozilla.org/en-US/firefox/addon/cookie-autode...
The thing about "new container by default", is that sessions are always lost, and people generally want to keep session alive.
Re: An Update on Firefox Containers
#39I still think multiple profiles are a better choice. My main profile never keeps cookies and have a very rigid https://github.com/pyllyukko/user.js file and only a couple of extensions. I'm very scared about extensions and self-updating scripts so I only keep them isolated. It also helps with organization since I have different bookmarks. I can also "firewall" that profile to never accidentally load websites I don't want to.
If needed you can drag windows/tabs between profiles or even other browsers. I disabled all the referral options too.
Re: An Update on Firefox Containers
#40i love containers, but keyboard usage is still not ideal (i had submitted a feature request for this via github a while back). they landed on using ctrl-. (control-period) to open the containers dropdown and then you have to tab to the container you want. not only does this require two hands, but even tanvi in the blog post admits this is not discoverable at all. ideally, you could have a single hand command (like cm…
This was exactly the feedback I had provided on a previous HN post a few weeks ago. At that time, one of the developers suggested filing an issue for it. I didn’t get around to doing that at all. Maybe you could consider doing that, or I’ll do it in about a couple of weeks.