mozilla
Allow Multi-Account-Containers in Private Browsing Mode
There are some feature requests to allow a special "private mode" container.
This is a feature request to do the opposite. It proposes a scenario where the browser is opened in private mode (privacy by default), and then allow the user to select a container from within private mode when they want to be identifiable.
Currently, this extension does not operate in private mode at all, which means all of my daily browsing [not in a container] is still being tracked and profiles being built up across months of usage. I could create a container for daily browsing, but a profile would still be built up in that container. I could delete and re-create that container from time to time, but that is a manual intervention that would be best to be avoided.
So this proposal is to allow the browser to be opened in private mode, and then allow to open a container only when I need it.
Under this proposal, I would have first browsed the github repo in private mode, and then once I decided I wanted to submit this feature request, opened my github container in a new tab, but still in the private window.
One use of private containers is to protect your bank account password, but another use is to protect your browsing history (and trackers ability to link your disparate actions together). This proposal is about protecting your browsing history, and not your bank account password.
This would absolutely be ideal, but also can't be implemented as an extension. It requires changes to Firefox itself. I approximate that behaviour by enabling first party isolation and using cookie auto-delete to erase application data except for specific sites in specific containers, but it's a clunky solution for sure.
Private mode definitely has its advantages but when it comes to first party cookies, it falls short. For this reason, PB in along with containers, Firefox will bring extra privacy to the table.
I was wondering, if there is some update on a potential timeline or if this request if off the table for now?
You may want to try this new extension: Open in Temp Container. Give it permission to access your browsing history too for it to prevent new URLs opened in temporary containers from being stored.
Thank you for posting this that might really help in my case.
@dannycolin is there any chance that this will get addressed any time soon? I am fully aware that this is not high-prio but I really would like to see it supported in the future.
It needs to be implemented in Firefox itself but no one is actively working on containers (See bug 1320757).
Looking at the upstream bug, it seems like containers in a private window aren't linked to their counterpart in a regular window. This means your "Personal" container would be different than your private "Personal" which was confusing to people and the reason why it was disabled.
