[rdimartino]

This is great. I’ve been using multi-account containers for years and have loved the isolation. But I wonder how Total Cookie Protection works with different auth flows, like logging in to Trello using an Atlassian domain. Maybe it’s unaffected; I haven’t really looked at how/if cookies are involved in that process, but I can imagine TCP causing some frustration for users. Definitely will give it a shot, though.

[codedokode]

I think third-party cookies should be disabled out of the box but there should be an option to manually allow them for legacy applications (if there are popular legacy applications then Firefox could include some of them by default).

[dylan604]

Using what, the legacy app flag?

[beej71]

Local domain whitelist? Would that work?

[dylan604]

Created by the user? Like, who's going to go out of their way to create a whitelist of associated websites so it's okay to share across those sites?

So, I'm totally on board for this! The only other thing would be to just not let cross domain sharing. at. all.

[KennyBlanken]

Which of course wouldn't be abused. Either set willy-nilly, or companies purposefully implementing broken methods to get an exemption so their tracking cookies work /s

[dylan604]

If that frustration means that I have to log in with the same creds to two sites like Atlassian and Trello, then I'm okay with that. In fact, I would really like it if I didn't have to go to Atlassian at all and just be able to log in to Trello itself. But that's a different topic entirely. For the great majority of people it's the same email and password for every site they visit, so it's easy for them. Then there's the other end of the spectrum of people that use password managers and have dedicated credentials for every site, but it's also no big deal for them because they use the password manager to handle it.

[cqqxo4zV46cp]

Yeah, especially if we’re calling it TCP! :)