<html>
<head>
<base href="https://bugs.webkit.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Recent change in ITP2 behaviour blocks 3rd party cookies"
href="https://bugs.webkit.org/show_bug.cgi?id=189045#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Recent change in ITP2 behaviour blocks 3rd party cookies"
href="https://bugs.webkit.org/show_bug.cgi?id=189045">bug 189045</a>
from <span class="vcard"><a class="email" href="mailto:wilander@apple.com" title="John Wilander <wilander@apple.com>"> <span class="fn">John Wilander</span></a>
</span></b>
<pre>Partitioned cookies were removed here (motivations explained in the bug): <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED FIXED - Resource Load Statistics: Remove partitioned cookies for reduced complexity, lower memory footprint, and ability to support more platforms"
href="show_bug.cgi?id=188109">https://bugs.webkit.org/show_bug.cgi?id=188109</a>
With this change, being blocked in third-party contexts doesn't necessarily mean cookies and website data is purged though. If the domain has received user interaction the last 30 days of use, as first party or through successful use of the Storage Access API, its cookies are not purged.
Are you saying your domain's cookies are being purged even though your domain has received fresh user interaction?</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>