This needs to be a discussion with the other browsers. The remedies and
timescale will also depend on how things shake out during the third-party
cookie deprecation over the next year. These are the reasons we have
not set an end date right now. Any date would be somewhat arbitrary
pending
While this is approved, I do have a followup question about:
> we intend to eventually retire these heuristics as alternative
solutions become widely used, subject to further feasibility analysis.
In many other plans there have been dates or milestones mentioned, and
even though they have
LGTM3
On Tuesday, December 5, 2023 at 6:53:30 PM UTC+1 Rick Byers wrote:
> LGTM2
>
> Thank you for putting the extra rigor and effort into trying to specify
> and align on this behavior, rather than just copy the precedent set by the
> other two engines in relying on non-standards-track
LGTM2
Thank you for putting the extra rigor and effort into trying to specify and
align on this behavior, rather than just copy the precedent set by the
other two engines in relying on non-standards-track heuristics! It's
exactly in these messy real-world examples of web behavior that our
I see this as a critical web compatibility intervention, so LGTM1.
It seems like there is some disagreement about spec venue (compat vs
fetch/html), but I don't think we need to block on landing given the
other browsers shipped their heuristics without specifying in any
standards venue.
Contact emails
amal...@chromium.org
johann...@chromium.org
rtarp...@chromium.org
wanderv...@chromium.org
Explainer
https://github.com/amaliev/3pcd-exemption-heuristics/blob/main/explainer.md
Specification
Pull request: https://github.com/whatwg/compat/pull/253
Summary
This proposal
