Spec (Copied from I2E)
Summary (Copied from I2E)
Link to “Intent to Prototype” blink-dev discussion (Copied from I2E)
Goals for experimentation (Copied from I2E)
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 June 14, 2022.
We would like to extend the experiment through M104; or in other words, until the release of M105, which is August 30th, 2022.
Any risks when the experiment finishes? (Copied from I2E)
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 are talking to multiple interested testing partners, with different use cases, who have requested additional time to prepare for the origin trial, and test the feature. Extending the trial would allow us to gather more feedback across more use cases.
We discovered a bug that prevents Origin Trial opt-in from third-party contexts, which is the typical configuration to use the feature. This bug has been fixed in M103.
We have received feedback that the current origin trial opt-in mechanism is difficult to deploy for large organizations. We have proposed an update to the design of this mechanism, which we aim to release in M103.
Ongoing technical constraints (Copied from I2E)
Debuggability (Copied from I2E)
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 I2E)
Link to entry on the feature dashboard (Copied from I2E)
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/CAMCNMFSx%3DLnTJGOGt0S5GnefQGGEhtea5tUxFkix%3DKYFDxZbyQ%40mail.gmail.com.
I am reaching out to announce some changes to the Cookies Having Independent Partitioned State (CHIPS) origin trial. Starting in Chrome 104, we will be removing the no-Domain requirement for cookies set with the Partitioned attribute. This means that cookies with the Partitioned attribute can now be scoped such that all subdomains on the domain can set and receive the same partitioned cookie. Cookies set with Partitioned still must use the Secure and Path=/ attributes.
We have received feedback from partners telling us that the requirement was making adopting and testing CHIPS more difficult. Therefore, we have decided to remove the requirement for the origin trial to allow developers to test and prepare their sites for the phasing out of unpartitioned third-party cookies in a timely manner. Please note that the change has not been finalized for shipping. The decision on final shipping behavior will be made following further discussion on the explainer issue. Please provide feedback on the linked GitHub issue, or on this thread if this change impacts you.