Yeah, but I mean before they implement this scheme, I hope they modify the browser (or someone comes up with one), so that you can pick which group of cookies are accessible within different tabs.

With apps, I know that this app doesn't know my identity from that app unless I explicitly give it permissions.

Firefox is starting a project on this, it's still in research stages though. https://blog.mozilla.org/tanvi/2016/06/16/contextual-identit... In the meantime, you can use different user profiles in Chrome or Firefox, but they work per-window not per-tab.

Great news. Thanks. Didn't realize that Chrome and Firefox do that on a per-window basis. I browse everything in incognito mode.

Firefox is working on it, you can try it in the nightlies, at least as of this post: https://blog.mozilla.org/tanvi/2016/06/16/contextual-identit...

thanks.

actually a cookie is still only accessible if its on the same origin or on a subdomain of the origin.

I did not realize that. If that is so, why is Firefox working on the tab-cookie isolation (see other answers).

This is mentioned in that blog post, but data is separated by a tuple of: (scheme e.g. HTTP or HTTPS, domain, port). Any page from one such set cannot access cookies, local storage, indexeddb, or cache from a page with a different set. The new feature simply adds one more attribute, so even if pages share scheme, domain, and port, they will not be able to read data from a site with a different userContextId.

thats more to seperate work and private data. I.e. at the moment you can't login to Office 365 twice. With a tab isolation level it would work. But actually its more like a container which you can assign to multiple tabs. you could start a tab with the container private or with the container xyz