Hello Chris I have had the worst luck with the 3rd party cookies. They've infested my accounts, so I can't log in. Or use my credit cards online. I think you should contact me as soon as possible. I'm not sure if you will receive this Thank you, Melissa 720-409-7391 testingmelis...@gmail.com On Tuesday, February 1, 2022 at 12:14:29 PM UTC-7 Dylan Cutler wrote:
> Contact emails > > dylan...@google.com, kaust...@google.com > > Spec > > https://github.com/WICG/CHIPS > > Summary > > 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 (or First-Party Set, where > the site uses that feature) 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 > > https://groups.google.com/a/chromium.org/g/blink-dev/c/hvMJ33kqHRo > > Goals for experimentation > > 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 > > The experiment will start in M100 and run from March 31st, 2022 until June > 30, 2022. > > Any risks when the experiment finishes? > > 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. > > Reason this experiment is being extended > > N/A > > Ongoing technical constraints > > None. > > Debuggability > > 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)? > > Yes. > > Link to entry on the feature dashboard <https://www.chromestatus.com/> > > https://www.chromestatus.com/feature/5179189105786880 > > -- 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+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/c201a517-e292-40a9-aebd-3ebed0d67f4dn%40chromium.org.
