131–140 of 142 posts
Earlier quoted context omitted.
yes, you could describe that use case as "quarantining" websites in short, but I'd say it's a power user feature if managed manually. If you install the "facebook container" extension, it's zero conf but it's only for facebook. Another use case I saw users being interested in, is you have 2 (or more) accounts on a website and you can login in both at the same time in 2 separate containers (you cannot quarantine the w…
So compared to a private tab, you basically get persistence and some form of organization (containers also act as groups). How important is to have tabs from different containers in the same window?
Earlier quoted context omitted.
Your decision to be a dismissive smartarse really annoyed me, because of course i'm not that much of an idiot. Turns out that like another respondent here, animesh, I had 'browser.proton.enabled' set to false too from an attempt to fix my tabs last time FF buggered around with things. Setting that to TRUE has got the colours on. So, only slightly an idiot...
When I see anecdotes like this, I better understand why Mozilla is moving away from about:config. A thousand variables makes issues far more difficult to debug.
Earlier quoted context omitted.
How is that different from anonymous browsing tabs?
Anon browsing allows max 2 separate simultaneous contexts: the anon session and your tracked session. This allows many different anon sessions. It's also a nicer more consistent integration if you already use (permanent) containers.
Will containers save your session when you close them and reopen them again later?
Earlier quoted context omitted.
How is that different from anonymous browsing tabs?
It's per tab not per window and they can coexist with trusted containers. It also has a non-automatic mode where you select sites that open in temporary containers instead of selecting sites that don't.
Sounds almost like you can have containers like profiles.
Where one tab is opened in a container signed in to an account and another signed into a different account.
Will containers save your session when you close them?
Earlier quoted context omitted.
Apart from the features in the sibling comment, your history will be kept.
As well as cookies between restarts, so eg. you don’t have to login to google inside your google container.
That means you can almost implement google profiles with containers.
Except it's kinda per tab instead of per window.
And that's really cool.
Am I conceptualizing that right?
Earlier quoted context omitted.
Anon browsing allows max 2 separate simultaneous contexts: the anon session and your tracked session. This allows many different anon sessions. It's also a nicer more consistent integration if you already use (permanent) containers.
That makes sense! Thanks for the info! Will containers save your session when you close them and reopen them again later?
The only thing I would love to see for containers is some sort of VPN that lets you connect through a different server on a specific container, and potentially isolated web history between containers. Then if I'm live streaming my browser to online strangers, one of the suggestions should be for anything personal (or if streaming to relatives / co-workers you don't expose your online life, which can be problematic to…
Hey there! I'm one of the devs on this project. We made some progress last year on per-container proxy support. Follow this issue for (hopefully soon) progress here: https://github.com/mozilla/multi-account-containers/pull/190...