- From: Johann Hofmann <notifications@github.com>
- Date: Tue, 24 May 2022 02:33:53 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 24 May 2022 09:34:05 UTC
I'm not @krgovind but as noted in https://github.com/privacycg/proposals/issues/30#issuecomment-1113257336 there's concrete interest from other browsers (than Chrome) in the proposal subject to a few details such as avoiding a tight integration with FPS in the spec, so that browsers may support CHIPS without also shipping FPS. I actually think the CHIPS explainer is already worded in a way that makes it work, i.e. saying: > Third parties which are embedded in multiple sites that are all in the same [First-Party Set](https://github.com/privacycg/first-party-sets) may use the same cookie jar partition across those sites. ...which isn't applicable for browsers that don't support FPS. I would still expect us to leave these parts out of the final CHIPS specification and patch them in FPS instead, while FPS is still under discussion. I think that's the expectation from other implementors as well. -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/654#issuecomment-1135654395 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/654/1135654395@github.com>
Received on Tuesday, 24 May 2022 09:34:05 UTC