> This would be for sites on some kind of tracking list that start out without any kind of storage? Because I think ideally this would be the default. (Even more ideal would be if we didn't need the lists long term as the partitioning would keep it all in check.)

[patrron]

          > This would be for sites on some kind of tracking list that start out without any kind of storage? Because I think ideally this would be the default. (Even more ideal would be if we didn't need the lists long term as the partitioning would keep it all in check.)

As mentioned in the issue and on Privacy CG calls, WebKit has seen compatibility issues for partitioned cookies. A solution for that is to make cross-site embedees explicitly opt in to partitioned cookies while blocking their cookies by default.

WebKit+CFNetwork has blocked pure cross-site cookies for 18 years with the exception of 2017-2018 when we tried partitioned cookies. For us, partitioned cookies by default only leads to more cookies.

The proposal here is to allow browsers to block cross-site cookies by default and give developers an explicit way of opting into them. The blocking can be based on whatever the browser wants, including lists.

Originally posted by @johnwilander in #75 (comment)