Add ability to set a default container for new windows and tabs

[andreicristianpetcu]

Right now we can have stuff like all reddit and github be opened in my "Personal" container.
It would be really cool to have all tabs that do not match any container to go to a "Default" container.

If all new tabs are always in containers, addons can do really cool stuff like delete the "Default" container on exit and re create it again on startup. This would basically create a private tab (in a private browsing sense) for all web sites that are not assigned in a container.

This would really bring painless tracking protection to the masses and really nice privacy.

┆Issue is synchronized with this Jira Task

[jonathanKingston]

Are you referring to:

a. Links within a container tab that are not "assigned" to a container opening in a "Default" tab
b. The fact all normal tabs are not a container?

a. I think this has been spoken about before, certainly this is something I would like the option to be able to specify.

b. Currently non container tabs are available to be differentiated from container tabs by extensions using cookieStoreId when checking cookies or tabs etc.

For b. Are you expecting normal tabs to be highlighted or that extensions break soon as containers are installed, meaning they have to be specific to target "Default" containers?

[andreicristianpetcu]

I am refering to b.. I would like all tabs to be in a container. This would create uniformity. Right now there is a check if the web site I am going to open or the link I am clicking is matched to a container. If I match Facebook.com to my Personal container, then all links inside Facebook will be opened in that container.

If I do not map Facebook to any container, then it will be opened outside any container. I would like to exist a catch all container named Default. If a web site does not match any container I would like it to be matched to a preexisting container named "Default".

I'm not sure if I build an extension that puts all non-container tabs inside a Default container if it will break when Tab Containers will land in stable. What if my WebExtension gets to decide first what container Facebook will be part of? If it gets to decide before testpilot-containers then all new tabs will ignore testpilot-containers mapping and will be part of the Default container.

I don't care about UI. If this Default container is looks like normal tab or a glowing container tab it is ok with me. I only care about cookies and other type of storage. I would like to have some sort of disposable container for all tabs that are not mapped to any container. This can be like a private tab of some sort. Firefox can now delete all sorts of data on exit, I would like it to delete and recreate the Default container as part of an extension but I need tab containers to be able to send all new tabs to a default container.

If I go to Facebook and it is mapped to Personal and I click on a reddit link pointing to https://theintercept.com and theintercept is not mapped to any container, I would like it to be opened inside the Default one.

[jonathanKingston]

This actually seems like a duplicate of: #434

Where by:

• User opens work
• User goes to google.com
• User clicks a link to other.com
• New default tab is created to other.com

If you don't care about the UI then we can just use default tabs here, the issue is around when links open default over the current container right?

Is this even specific to assignment, other than that makes it easier to use if this was the default behaviour.

Can I close this as duplicate or do you think it is different?

[grahamperrin]

#573 (comment)

b.. I would like all tabs to be in a container.

Please try Always In Container; there's a screenshot at https://bugzilla.mozilla.org/show_bug.cgi?id=1692124#c1

[dannycolin]

It isn't a duplicate. I get Andrei idea. Instead of having a "no container storage" the browser would open in a "default container storage" on startup. This way you can benefit from the ContextualIdentity API to manipulate this tabs. For example, "hide all" option in MAC could be used on them while it's currently not possible since they're considered outside the container context.

In theory, the implementation will look like: When a new tab or window is opened, look if it's assigned to a container. If not, open it in the "default container". The default container could be hardcoded (meh) or we could add an option for the user to choose which container from their list should be considered the default one.