Can all tabs be isolated/containarised by default?

[encodinge]

This is a proposal for a new way to utilising the containers/jars feature:

You may want amazzon.com and amazzon.be to share cookies and data so that you dont have to login for each domain.
You may not want mail.gogle.com with maps.gogle.com to share cookies and data.

But it quite difficult and cumbersome to maintain all such containers.

So, perhaps the best use of containerization and cookie jars would be to:

1. By default containerize every tab by default as if you open it without any other tab opened in the browser and with cleared browser history etc.
2. If the tab opened "attempts" to access data/cookies of same or other domains, ASK the user to allow. Also, offer the user to store their choice. E.g. amazzon.com can access amazzon.be cookies but mail.gogle.com should not access maps.gogle.com cookies.
3. To prevent too many questions, you can have a discreet way for user to check if the website wants to read other (or older own) cookies.

Is that possible?

Thanks!

[FaFre]

You can configure a site assignment to a container "Amazon" for amazzon.com and amazzon.be so every time you open one of the sites the will get automatically assigned to your container. Will that already solve your issue?

[encodinge]

Not exactly.
Basically, I need to containarize (isolate if you like) each and every website I visit from all other websites/cookies.

The problem of course becomes when you open a tab for domain.com and you click to open links. Would these be containarized too?

1. YES if they are external links
2. PERHAPS if they are internal links (e.g. website.com/page2) as you may need to reuse the cookie, login info from website.com

At the same time, some domains are identical but you would still need to isolate them from each other like onedrive.com/drive1 and onedrive.com/drive2

It can get complex though, that's why I proposed to give the WebLibre user the option to isolate by default and then choose to group/share cookies when they feel so: At the moment, WebLibre does NOT isolate by default. Private tabs are an option but the major issue is they are not reopened upon browser restart.

[FaFre]

Well if you want to have the same behavior as private tabs, (exclude closing on browser restart) just use a container with cookie isolation, that will be effectively the same.

[encodinge]

Well if you want to have the same behavior as private tabs, (exclude closing on browser restart) just use a container with cookie isolation, that will be effectively the same.

My impression was that the "Cookie isolation" setting within a container means that all the tabs of the container will share a common cookie jar (so all tabs in that container will be able to 'see' cookies from each other).

This is very different from "each tab of the container will have its own cookie jar"?