CHIPS Intent to Extend Experiment
Dylan Cutler
Contact emails
dylan...@google.com, kaust...@google.com
Spec (Copied from prior I2EE)
Summary (Copied from prior I2EE)
Given that Chrome plans on obsoleting unpartitioned third-party cookies, we want to give developers the ability to use cookies in cross-site contexts that are partitioned by top-level site to meet use cases that are not cross-site tracking related (e.g. SaaS embeds, headless CMS, sandbox domains, etc.). In order to do so, we introduce a mechanism to opt-in to having their third-party cookies partitioned by top-level site using a new cookie attribute, Partitioned.
Link to “Intent to Prototype” blink-dev discussion (Copied from prior I2EE)
https://groups.google.com/a/chromium.org/g/blink-dev/c/hvMJ33kqHRo
Goals for experimentation (Copied from prior I2EE)
CHIPS is a new, opt-in technology meant to preserve a set of use cases (e.g. third-party embeds) that may break once third-party cookies are phased out while preventing cross-site tracking. We need to validate whether the proposed syntax and semantics solve these use cases prior to third-party cookie obsoletion by giving developers a way to test it in a scaled manner and provide early feedback. We hope to validate ergonomics, deployability, and backward compatibility.
Experimental timeline (Modified)
The experiment started in M100 and started on March 29th, 2022 and is currently scheduled to run until August 30, 2022.
We would like to extend the experiment through M106; or in other words, until the stable release of M107, which is October 25th, 2022.
Any risks when the experiment finishes? (Copied from prior I2EE)
Since Chrome will not send and may delete partitioned cookies when it is started with the feature disabled, sites that set cookies with the Partitioned attribute during the experiment will no longer have those cookies available on clients' machines.
Reasons this experiment is being extended (New)
We received feedback [1][2] that the no-Domain attribute requirement was making CHIPS more difficult to adopt for site developers. We landed a change in M104 which removes the requirement that Partitioned cookies do not include the Domain attribute, so we want to give partners more time to test CHIPS now that this restriction has been lifted.
Ongoing technical constraints (Copied from prior I2EE)
None.
Debuggability (Copied from prior I2EE)
We have coordinated with the DevTools team to surface cookie partition keys to developers in DevTools. We have added a new cookie inclusion reason with a debug string when sites set Partitioned cookies incorrectly. We may also support surfacing partitioned cookies that are not included in requests because their partition key did not match the top-level site in DevTools.
Will this feature be supported on all five Blink platforms supported by Origin Trials (Windows, Mac, Linux, Chrome OS, and Android)? (Copied from prior I2EE)
Yes.
Link to entry on the feature dashboard (Copied from prior I2EE)
Yoav Weiss
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAMCNMFTDSG3pXQZrUHjM%2B%2BA8iEftje5n4vyfsJyWYvGSHnXwRg%40mail.gmail.com.