Re: [blink-dev] Request for Deprecation Trial: Deprecate Third-Party Cookies

['Johann Hofmann' via blink-dev]

Hi all, to follow up here, we're happy to share that the first-party 
Deprecation Trial (DT for top-level sites) for 3PCD is now available. See 
below resources for more details:

Announcement blog: 
https://developers.google.com/privacy-sandbox/blog/3pcd-first-party-deprecation-trial-available

Documentation: 
https://developers.google.com/privacy-sandbox/3pcd/temporary-exceptions/first-party-deprecation-trial

Thanks,
Johann

On Friday, January 19, 2024 at 9:26:23 PM UTC+1 wande...@chromium.org wrote:

> On Fri, Jan 19, 2024 at 2:27 PM Brett McStotts  
> wrote:
>
>> I'm interested in the first-party version of the 3PDC Deprecation Trial 
>> for top-level origins. I've already registered my domain for the DT for the 
>> third-party version. My token is technically already first-party; I did not 
>> enable "Third-party matching" as instructed 
>> 
>>  
>> under providing the token in an HTTP header. Can I use my existing token 
>> for the upcoming first-party version for top-level origins? Or will this be 
>> a separate registration process where I need a different token? 
>
>
> The upcoming first-party DT will be a separate trial and require a 
> separate token.
>
> Also note, the "Third-party matching" is only relevant to how you want to 
> deploy the token.  For the existing third-party DT clicking this option 
> allows you to deploy the token via a 3P script instead of on an embedded 
> iframe.
>  
>
>> On Wednesday, January 17, 2024 at 7:42:38 AM UTC-5 joha...@google.com 
>> wrote:
>>
>>> Hi all, a brief update that the team is still working on setting up the 
>>> first-party version of this Deprecation Trial.
>>>
>>> In the meantime, if you're a developer experiencing breakage on your 
>>> site and are planning to apply to the first-party DT, please file a 
>>> breakage report via https://goo.gle/report-3pc-broken at your earliest 
>>> convenience to support faster processing once the DT registration opens.
>>>
>>> Thanks,
>>>
>>> Johann
>>>
>>> On Tue, Dec 26, 2023 at 5:13 PM Chris Harrelson  
>>> wrote:
>>>
 LGTM

 On Tue, Dec 26, 2023 at 8:11 AM 'Joshua Hood' via blink-dev <
 blin...@chromium.org> wrote:

> Hi Blink API owners,
>
> We would like to request your approval for adding a first-party 
> version of this Deprecation Trial. This will be helpful for top-level 
> origins that also need additional transition time, in cases where it is 
> impossible, impractical or unnecessary to sign the affected third-party 
> (3P) providers up for the 3P deprecation trial. This deprecation trial 
> temporarily provides cross-site cookie access for non-advertising use 
> cases.
>
> This has been requested by web developers on threads such as the I2D 
> thread 
> 
>  
> for third-party cookies.
>
> Our proposed timelines for this trial remain unchanged:
>
> Registration opens the week of January 15, 2024 [1]
>
> The trial will end on December 27, 2024
>
> Effective in Chrome versions M120 through M132
>
> [1] As communicated previously, the grace period 
> 
>  
> that we are providing for the third-party deprecation trial also applies 
> to 
> the first-party deprecation trial. Additionally, to minimize user 
> impact before registration for the trial opens, Chrome will provide 
> temporary access to third-party cookies for sites with reported 
>  user-facing breakage during this 
> grace period.
>
> On Tuesday, December 5, 2023 at 3:53:04 PM UTC-5 Ben Kelly wrote:
>
>> FYI, we are also planning to provide a grace period for sites 
>> registered and approved for the deprecation trial to give them time to 
>> deploy trial tokens.  See this updated section of the blog post:
>>
>>
>> https://developers.google.com/privacy-sandbox/blog/third-party-cookie-deprecation-trial#:~:text=We%20acknowledge%20that,the%20grace%20period
>> .
>>
>> On Tue, Dec 5, 2023 at 12:22 PM Ben Kelly  
>> wrote:
>>
>>> The deprecation trial is now open for registrations:
>>>
>>>
>>> https://developer.chrome.com/origintrials/#/view_trial/3315212275698106369
>>>
>>> Again, please be aware this trial will require a review process as 
>>> outlined in the blog pos 
>>> 

Re: [blink-dev] Request for Deprecation Trial: Deprecate Third-Party Cookies

[Ben Kelly]

On Fri, Jan 19, 2024 at 2:27 PM Brett McStotts 
wrote:

> I'm interested in the first-party version of the 3PDC Deprecation Trial
> for top-level origins. I've already registered my domain for the DT for the
> third-party version. My token is technically already first-party; I did not
> enable "Third-party matching" as instructed
> 
> under providing the token in an HTTP header. Can I use my existing token
> for the upcoming first-party version for top-level origins? Or will this be
> a separate registration process where I need a different token?


The upcoming first-party DT will be a separate trial and require a separate
token.

Also note, the "Third-party matching" is only relevant to how you want to
deploy the token.  For the existing third-party DT clicking this option
allows you to deploy the token via a 3P script instead of on an embedded
iframe.


> On Wednesday, January 17, 2024 at 7:42:38 AM UTC-5 joha...@google.com
> wrote:
>
>> Hi all, a brief update that the team is still working on setting up the
>> first-party version of this Deprecation Trial.
>>
>> In the meantime, if you're a developer experiencing breakage on your site
>> and are planning to apply to the first-party DT, please file a
>> breakage report via https://goo.gle/report-3pc-broken at your earliest
>> convenience to support faster processing once the DT registration opens.
>>
>> Thanks,
>>
>> Johann
>>
>> On Tue, Dec 26, 2023 at 5:13 PM Chris Harrelson 
>> wrote:
>>
>>> LGTM
>>>
>>> On Tue, Dec 26, 2023 at 8:11 AM 'Joshua Hood' via blink-dev <
>>> blin...@chromium.org> wrote:
>>>
 Hi Blink API owners,

 We would like to request your approval for adding a first-party version
 of this Deprecation Trial. This will be helpful for top-level origins
 that also need additional transition time, in cases where it is impossible,
 impractical or unnecessary to sign the affected third-party (3P) providers
 up for the 3P deprecation trial. This deprecation trial temporarily
 provides cross-site cookie access for non-advertising use cases.

 This has been requested by web developers on threads such as the I2D
 thread
 
 for third-party cookies.

 Our proposed timelines for this trial remain unchanged:

 Registration opens the week of January 15, 2024 [1]

 The trial will end on December 27, 2024

 Effective in Chrome versions M120 through M132

 [1] As communicated previously, the grace period
 
 that we are providing for the third-party deprecation trial also applies to
 the first-party deprecation trial. Additionally, to minimize user
 impact before registration for the trial opens, Chrome will provide
 temporary access to third-party cookies for sites with reported
  user-facing breakage during this
 grace period.

 On Tuesday, December 5, 2023 at 3:53:04 PM UTC-5 Ben Kelly wrote:

> FYI, we are also planning to provide a grace period for sites
> registered and approved for the deprecation trial to give them time to
> deploy trial tokens.  See this updated section of the blog post:
>
>
> https://developers.google.com/privacy-sandbox/blog/third-party-cookie-deprecation-trial#:~:text=We%20acknowledge%20that,the%20grace%20period
> .
>
> On Tue, Dec 5, 2023 at 12:22 PM Ben Kelly 
> wrote:
>
>> The deprecation trial is now open for registrations:
>>
>>
>> https://developer.chrome.com/origintrials/#/view_trial/3315212275698106369
>>
>> Again, please be aware this trial will require a review process as
>> outlined in the blog pos
>> 
>> t.
>>
>> On Tue, Nov 21, 2023 at 2:53 PM Ben Kelly 
>> wrote:
>>
>>> FYI, please see this blog post for more information on this
>>> deprecation trial:
>>>
>>>
>>> https://developer.chrome.com/blog/third-party-cookie-deprecation-trial/
>>>
>>> On Fri, Nov 17, 2023 at 7:52 PM Mike Taylor 
>>> wrote:
>>>
 LGTM for a deprecation trial from M120 to M132. For those of you
 who have followed my career (all 2 of you), it shouldn't come as a 
 surprise
 that I appreciate the desire and efforts to minimize the compat
 implications for sites that are earnestly moving towards 

Re: [blink-dev] Request for Deprecation Trial: Deprecate Third-Party Cookies

[Brett McStotts]

I'm interested in the first-party version of the 3PDC Deprecation Trial for 
top-level origins. I've already registered my domain for the DT for the 
third-party version. My token is technically already first-party; I did not 
enable "Third-party matching" as instructed 

 
under providing the token in an HTTP header. Can I use my existing token 
for the upcoming first-party version for top-level origins? Or will this be 
a separate registration process where I need a different token? 
On Wednesday, January 17, 2024 at 7:42:38 AM UTC-5 joha...@google.com wrote:

> Hi all, a brief update that the team is still working on setting up the 
> first-party version of this Deprecation Trial.
>
> In the meantime, if you're a developer experiencing breakage on your site 
> and are planning to apply to the first-party DT, please file a 
> breakage report via https://goo.gle/report-3pc-broken at your earliest 
> convenience to support faster processing once the DT registration opens.
>
> Thanks,
>
> Johann
>
> On Tue, Dec 26, 2023 at 5:13 PM Chris Harrelson  
> wrote:
>
>> LGTM
>>
>> On Tue, Dec 26, 2023 at 8:11 AM 'Joshua Hood' via blink-dev <
>> blin...@chromium.org> wrote:
>>
>>> Hi Blink API owners,
>>>
>>> We would like to request your approval for adding a first-party version 
>>> of this Deprecation Trial. This will be helpful for top-level origins 
>>> that also need additional transition time, in cases where it is impossible, 
>>> impractical or unnecessary to sign the affected third-party (3P) providers 
>>> up for the 3P deprecation trial. This deprecation trial temporarily 
>>> provides cross-site cookie access for non-advertising use cases.
>>>
>>> This has been requested by web developers on threads such as the I2D 
>>> thread 
>>> 
>>>  
>>> for third-party cookies.
>>>
>>> Our proposed timelines for this trial remain unchanged:
>>>
>>> Registration opens the week of January 15, 2024 [1]
>>>
>>> The trial will end on December 27, 2024
>>>
>>> Effective in Chrome versions M120 through M132
>>>
>>> [1] As communicated previously, the grace period 
>>> 
>>>  
>>> that we are providing for the third-party deprecation trial also applies to 
>>> the first-party deprecation trial. Additionally, to minimize user 
>>> impact before registration for the trial opens, Chrome will provide 
>>> temporary access to third-party cookies for sites with reported 
>>>  user-facing breakage during this 
>>> grace period.
>>>
>>> On Tuesday, December 5, 2023 at 3:53:04 PM UTC-5 Ben Kelly wrote:
>>>
 FYI, we are also planning to provide a grace period for sites 
 registered and approved for the deprecation trial to give them time to 
 deploy trial tokens.  See this updated section of the blog post:


 https://developers.google.com/privacy-sandbox/blog/third-party-cookie-deprecation-trial#:~:text=We%20acknowledge%20that,the%20grace%20period
 .

 On Tue, Dec 5, 2023 at 12:22 PM Ben Kelly  
 wrote:

> The deprecation trial is now open for registrations:
>
>
> https://developer.chrome.com/origintrials/#/view_trial/3315212275698106369
>
> Again, please be aware this trial will require a review process as 
> outlined in the blog pos 
> 
> t.
>
> On Tue, Nov 21, 2023 at 2:53 PM Ben Kelly  
> wrote:
>
>> FYI, please see this blog post for more information on this 
>> deprecation trial:
>>
>>
>> https://developer.chrome.com/blog/third-party-cookie-deprecation-trial/
>>
>> On Fri, Nov 17, 2023 at 7:52 PM Mike Taylor  
>> wrote:
>>
>>> LGTM for a deprecation trial from M120 to M132. For those of you who 
>>> have followed my career (all 2 of you), it shouldn't come as a surprise 
>>> that I appreciate the desire and efforts to minimize the compat 
>>> implications for sites that are earnestly moving towards this brave new 
>>> post-3rd-party cookies world. 
>>>
>>> (Note: I don't work on third-party cookie deprecation but I would 
>>> have landed on a similarly recommended timeline for 
>>> migration/deprecation. 
>>> Thanks for being accommodating and realistic to the complicated demands 
>>> of 
>>> web development and deployment of different use-cases.)
>>>
>>> On 11/17/23 1:21 PM, Ben Kelly wrote:

Re: [blink-dev] Request for Deprecation Trial: Deprecate Third-Party Cookies

['Johann Hofmann' via blink-dev]

Hi all, a brief update that the team is still working on setting up the
first-party version of this Deprecation Trial.

In the meantime, if you're a developer experiencing breakage on your site
and are planning to apply to the first-party DT, please file a
breakage report via https://goo.gle/report-3pc-broken at your earliest
convenience to support faster processing once the DT registration opens.

Thanks,

Johann

On Tue, Dec 26, 2023 at 5:13 PM Chris Harrelson 
wrote:

> LGTM
>
> On Tue, Dec 26, 2023 at 8:11 AM 'Joshua Hood' via blink-dev <
> blink-dev@chromium.org> wrote:
>
>> Hi Blink API owners,
>>
>> We would like to request your approval for adding a first-party version
>> of this Deprecation Trial. This will be helpful for top-level origins
>> that also need additional transition time, in cases where it is impossible,
>> impractical or unnecessary to sign the affected third-party (3P) providers
>> up for the 3P deprecation trial. This deprecation trial temporarily
>> provides cross-site cookie access for non-advertising use cases.
>>
>> This has been requested by web developers on threads such as the I2D
>> thread
>> 
>> for third-party cookies.
>>
>> Our proposed timelines for this trial remain unchanged:
>>
>> Registration opens the week of January 15, 2024 [1]
>>
>> The trial will end on December 27, 2024
>>
>> Effective in Chrome versions M120 through M132
>>
>> [1] As communicated previously, the grace period
>> 
>> that we are providing for the third-party deprecation trial also applies to
>> the first-party deprecation trial. Additionally, to minimize user impact
>> before registration for the trial opens, Chrome will provide temporary
>> access to third-party cookies for sites with reported
>>  user-facing breakage during this
>> grace period.
>>
>> On Tuesday, December 5, 2023 at 3:53:04 PM UTC-5 Ben Kelly wrote:
>>
>>> FYI, we are also planning to provide a grace period for sites registered
>>> and approved for the deprecation trial to give them time to deploy trial
>>> tokens.  See this updated section of the blog post:
>>>
>>>
>>> https://developers.google.com/privacy-sandbox/blog/third-party-cookie-deprecation-trial#:~:text=We%20acknowledge%20that,the%20grace%20period
>>> .
>>>
>>> On Tue, Dec 5, 2023 at 12:22 PM Ben Kelly  wrote:
>>>
 The deprecation trial is now open for registrations:


 https://developer.chrome.com/origintrials/#/view_trial/3315212275698106369

 Again, please be aware this trial will require a review process as
 outlined in the blog pos
 
 t.

 On Tue, Nov 21, 2023 at 2:53 PM Ben Kelly 
 wrote:

> FYI, please see this blog post for more information on this
> deprecation trial:
>
> https://developer.chrome.com/blog/third-party-cookie-deprecation-trial/
>
> On Fri, Nov 17, 2023 at 7:52 PM Mike Taylor 
> wrote:
>
>> LGTM for a deprecation trial from M120 to M132. For those of you who
>> have followed my career (all 2 of you), it shouldn't come as a surprise
>> that I appreciate the desire and efforts to minimize the compat
>> implications for sites that are earnestly moving towards this brave new
>> post-3rd-party cookies world.
>>
>> (Note: I don't work on third-party cookie deprecation but I would
>> have landed on a similarly recommended timeline for 
>> migration/deprecation.
>> Thanks for being accommodating and realistic to the complicated demands 
>> of
>> web development and deployment of different use-cases.)
>>
>> On 11/17/23 1:21 PM, Ben Kelly wrote:
>>
>> Contact emails
>>
>> joha...@chromium.org, wande...@chromium.org
>>
>> Explainer
>>
>> None
>>
>> Specification
>>
>>
>> https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-rfc6265bis-12#name-the-cookie-header-field
>>
>> Summary
>>
>> We intend to deprecate and remove default access to third-party (aka
>> cross-site) cookies as part of the Privacy Sandbox Timeline for the Web,
>> starting with an initial 1% testing period in Q1 2024, followed by a
>> gradual phaseout planned to begin in Q3 2024 after consultation with the
>> CMA. (The gradual phaseout is subject to addressing any remaining
>> competition concerns of the UK’s Competition and Markets Authority.)
>>
>> Phasing out third-party cookies (3PCs) is a central effort to the
>> Privacy Sandbox initiative, which aims to responsibly reduce cross-site
>> tracking on the web (and beyond) while supporting key use cases through 
>> new
>> technologies. Our phaseout plan was 

Re: [blink-dev] Request for Deprecation Trial: Deprecate Third-Party Cookies

[Chris Harrelson]

LGTM

On Tue, Dec 26, 2023 at 8:11 AM 'Joshua Hood' via blink-dev <
blink-dev@chromium.org> wrote:

> Hi Blink API owners,
>
> We would like to request your approval for adding a first-party version of
> this Deprecation Trial. This will be helpful for top-level origins that
> also need additional transition time, in cases where it is impossible,
> impractical or unnecessary to sign the affected third-party (3P) providers
> up for the 3P deprecation trial. This deprecation trial temporarily
> provides cross-site cookie access for non-advertising use cases.
>
> This has been requested by web developers on threads such as the I2D
> thread
> 
> for third-party cookies.
>
> Our proposed timelines for this trial remain unchanged:
>
> Registration opens the week of January 15, 2024 [1]
>
> The trial will end on December 27, 2024
>
> Effective in Chrome versions M120 through M132
>
> [1] As communicated previously, the grace period
> 
> that we are providing for the third-party deprecation trial also applies to
> the first-party deprecation trial. Additionally, to minimize user impact
> before registration for the trial opens, Chrome will provide temporary
> access to third-party cookies for sites with reported
>  user-facing breakage during this grace
> period.
>
> On Tuesday, December 5, 2023 at 3:53:04 PM UTC-5 Ben Kelly wrote:
>
>> FYI, we are also planning to provide a grace period for sites registered
>> and approved for the deprecation trial to give them time to deploy trial
>> tokens.  See this updated section of the blog post:
>>
>>
>> https://developers.google.com/privacy-sandbox/blog/third-party-cookie-deprecation-trial#:~:text=We%20acknowledge%20that,the%20grace%20period
>> .
>>
>> On Tue, Dec 5, 2023 at 12:22 PM Ben Kelly  wrote:
>>
>>> The deprecation trial is now open for registrations:
>>>
>>>
>>> https://developer.chrome.com/origintrials/#/view_trial/3315212275698106369
>>>
>>> Again, please be aware this trial will require a review process as
>>> outlined in the blog pos
>>> 
>>> t.
>>>
>>> On Tue, Nov 21, 2023 at 2:53 PM Ben Kelly  wrote:
>>>
 FYI, please see this blog post for more information on this deprecation
 trial:

 https://developer.chrome.com/blog/third-party-cookie-deprecation-trial/

 On Fri, Nov 17, 2023 at 7:52 PM Mike Taylor 
 wrote:

> LGTM for a deprecation trial from M120 to M132. For those of you who
> have followed my career (all 2 of you), it shouldn't come as a surprise
> that I appreciate the desire and efforts to minimize the compat
> implications for sites that are earnestly moving towards this brave new
> post-3rd-party cookies world.
>
> (Note: I don't work on third-party cookie deprecation but I would have
> landed on a similarly recommended timeline for migration/deprecation.
> Thanks for being accommodating and realistic to the complicated demands of
> web development and deployment of different use-cases.)
>
> On 11/17/23 1:21 PM, Ben Kelly wrote:
>
> Contact emails
>
> joha...@chromium.org, wande...@chromium.org
>
> Explainer
>
> None
>
> Specification
>
>
> https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-rfc6265bis-12#name-the-cookie-header-field
>
> Summary
>
> We intend to deprecate and remove default access to third-party (aka
> cross-site) cookies as part of the Privacy Sandbox Timeline for the Web,
> starting with an initial 1% testing period in Q1 2024, followed by a
> gradual phaseout planned to begin in Q3 2024 after consultation with the
> CMA. (The gradual phaseout is subject to addressing any remaining
> competition concerns of the UK’s Competition and Markets Authority.)
>
> Phasing out third-party cookies (3PCs) is a central effort to the
> Privacy Sandbox initiative, which aims to responsibly reduce cross-site
> tracking on the web (and beyond) while supporting key use cases through 
> new
> technologies. Our phaseout plan was developed with the UK's Competition 
> and
> Markets Authority, in line with the commitments we offered for Privacy
> Sandbox for the web.
>
> To support this effort we would like to run a deprecation trial for
> third-party embedded content.  Qualified third-parties participating in 
> the
> trial can supply a token via an iframe or third-party script in order to
> continue receiving third-party cookies on requests to that origin.
>
> Goals for experimentation
>
> The primary goal of the deprecation trial is to reduce the amount of
> broken 

Re: [blink-dev] Request for Deprecation Trial: Deprecate Third-Party Cookies

['Joshua Hood' via blink-dev]

Hi Blink API owners,

We would like to request your approval for adding a first-party version of 
this Deprecation Trial. This will be helpful for top-level origins that 
also need additional transition time, in cases where it is impossible, 
impractical or unnecessary to sign the affected third-party (3P) providers 
up for the 3P deprecation trial. This deprecation trial temporarily 
provides cross-site cookie access for non-advertising use cases.

This has been requested by web developers on threads such as the I2D 
thread 

 
for third-party cookies.

Our proposed timelines for this trial remain unchanged:

Registration opens the week of January 15, 2024 [1]

The trial will end on December 27, 2024

Effective in Chrome versions M120 through M132

[1] As communicated previously, the grace period 

 
that we are providing for the third-party deprecation trial also applies to 
the first-party deprecation trial. Additionally, to minimize user impact 
before registration for the trial opens, Chrome will provide temporary 
access to third-party cookies for sites with reported 
 user-facing breakage during this grace 
period.

On Tuesday, December 5, 2023 at 3:53:04 PM UTC-5 Ben Kelly wrote:

> FYI, we are also planning to provide a grace period for sites registered 
> and approved for the deprecation trial to give them time to deploy trial 
> tokens.  See this updated section of the blog post:
>
>
> https://developers.google.com/privacy-sandbox/blog/third-party-cookie-deprecation-trial#:~:text=We%20acknowledge%20that,the%20grace%20period
> .
>
> On Tue, Dec 5, 2023 at 12:22 PM Ben Kelly  wrote:
>
>> The deprecation trial is now open for registrations:
>>
>> https://developer.chrome.com/origintrials/#/view_trial/3315212275698106369
>>
>> Again, please be aware this trial will require a review process as 
>> outlined in the blog pos 
>> 
>> t.
>>
>> On Tue, Nov 21, 2023 at 2:53 PM Ben Kelly  wrote:
>>
>>> FYI, please see this blog post for more information on this deprecation 
>>> trial:
>>>
>>> https://developer.chrome.com/blog/third-party-cookie-deprecation-trial/
>>>
>>> On Fri, Nov 17, 2023 at 7:52 PM Mike Taylor  
>>> wrote:
>>>
 LGTM for a deprecation trial from M120 to M132. For those of you who 
 have followed my career (all 2 of you), it shouldn't come as a surprise 
 that I appreciate the desire and efforts to minimize the compat 
 implications for sites that are earnestly moving towards this brave new 
 post-3rd-party cookies world. 

 (Note: I don't work on third-party cookie deprecation but I would have 
 landed on a similarly recommended timeline for migration/deprecation. 
 Thanks for being accommodating and realistic to the complicated demands of 
 web development and deployment of different use-cases.)

 On 11/17/23 1:21 PM, Ben Kelly wrote:

 Contact emails 

 joha...@chromium.org, wande...@chromium.org

 Explainer 

 None

 Specification 


 https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-rfc6265bis-12#name-the-cookie-header-field

 Summary 

 We intend to deprecate and remove default access to third-party (aka 
 cross-site) cookies as part of the Privacy Sandbox Timeline for the Web, 
 starting with an initial 1% testing period in Q1 2024, followed by a 
 gradual phaseout planned to begin in Q3 2024 after consultation with the 
 CMA. (The gradual phaseout is subject to addressing any remaining 
 competition concerns of the UK’s Competition and Markets Authority.)

 Phasing out third-party cookies (3PCs) is a central effort to the 
 Privacy Sandbox initiative, which aims to responsibly reduce cross-site 
 tracking on the web (and beyond) while supporting key use cases through 
 new 
 technologies. Our phaseout plan was developed with the UK's Competition 
 and 
 Markets Authority, in line with the commitments we offered for Privacy 
 Sandbox for the web.

 To support this effort we would like to run a deprecation trial for 
 third-party embedded content.  Qualified third-parties participating in 
 the 
 trial can supply a token via an iframe or third-party script in order to 
 continue receiving third-party cookies on requests to that origin.

 Goals for experimentation 

 The primary goal of the deprecation trial is to reduce the amount of 
 broken user-visible experiences as third-party cookies are phased out.  
 Third-party embedded content or services with these kinds of experiences 
 can use the trial to continue to receive 

Re: [blink-dev] Request for Deprecation Trial: Deprecate Third-Party Cookies

[Ben Kelly]

FYI, we are also planning to provide a grace period for sites registered
and approved for the deprecation trial to give them time to deploy trial
tokens.  See this updated section of the blog post:

https://developers.google.com/privacy-sandbox/blog/third-party-cookie-deprecation-trial#:~:text=We%20acknowledge%20that,the%20grace%20period
.

On Tue, Dec 5, 2023 at 12:22 PM Ben Kelly  wrote:

> The deprecation trial is now open for registrations:
>
> https://developer.chrome.com/origintrials/#/view_trial/3315212275698106369
>
> Again, please be aware this trial will require a review process as
> outlined in the blog pos
> 
> t.
>
> On Tue, Nov 21, 2023 at 2:53 PM Ben Kelly  wrote:
>
>> FYI, please see this blog post for more information on this deprecation
>> trial:
>>
>> https://developer.chrome.com/blog/third-party-cookie-deprecation-trial/
>>
>> On Fri, Nov 17, 2023 at 7:52 PM Mike Taylor 
>> wrote:
>>
>>> LGTM for a deprecation trial from M120 to M132. For those of you who
>>> have followed my career (all 2 of you), it shouldn't come as a surprise
>>> that I appreciate the desire and efforts to minimize the compat
>>> implications for sites that are earnestly moving towards this brave new
>>> post-3rd-party cookies world.
>>>
>>> (Note: I don't work on third-party cookie deprecation but I would have
>>> landed on a similarly recommended timeline for migration/deprecation.
>>> Thanks for being accommodating and realistic to the complicated demands of
>>> web development and deployment of different use-cases.)
>>>
>>> On 11/17/23 1:21 PM, Ben Kelly wrote:
>>>
>>> Contact emails
>>>
>>> johann...@chromium.org, wanderv...@chromium.org
>>>
>>> Explainer
>>>
>>> None
>>>
>>> Specification
>>>
>>>
>>> https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-rfc6265bis-12#name-the-cookie-header-field
>>>
>>> Summary
>>>
>>> We intend to deprecate and remove default access to third-party (aka
>>> cross-site) cookies as part of the Privacy Sandbox Timeline for the Web,
>>> starting with an initial 1% testing period in Q1 2024, followed by a
>>> gradual phaseout planned to begin in Q3 2024 after consultation with the
>>> CMA. (The gradual phaseout is subject to addressing any remaining
>>> competition concerns of the UK’s Competition and Markets Authority.)
>>>
>>> Phasing out third-party cookies (3PCs) is a central effort to the
>>> Privacy Sandbox initiative, which aims to responsibly reduce cross-site
>>> tracking on the web (and beyond) while supporting key use cases through new
>>> technologies. Our phaseout plan was developed with the UK's Competition and
>>> Markets Authority, in line with the commitments we offered for Privacy
>>> Sandbox for the web.
>>>
>>> To support this effort we would like to run a deprecation trial for
>>> third-party embedded content.  Qualified third-parties participating in the
>>> trial can supply a token via an iframe or third-party script in order to
>>> continue receiving third-party cookies on requests to that origin.
>>>
>>> Goals for experimentation
>>>
>>> The primary goal of the deprecation trial is to reduce the amount of
>>> broken user-visible experiences as third-party cookies are phased out.
>>> Third-party embedded content or services with these kinds of experiences
>>> can use the trial to continue to receive third-party cookies while they
>>> work on long term solutions for their users based on CHIPS, Storage Access
>>> API, Related Website Sets, FedCM, etc.
>>>
>>> To meet this goal, requests to register for the deprecation trial will
>>> be reviewed to confirm eligibility. Specifically, third-party providers
>>> will need to demonstrate functional breakage in user journeys to be
>>> eligible. Because the deprecation trial is not intended to support
>>> cross-site tracking for advertising purposes, third-party embeds and
>>> services used for advertising will not be eligible. The ineligibility of
>>> advertising use cases will also help to ensure the deprecation trial does
>>> not interfere with the industry testing planned for the start of 2024 as
>>> described by the CMA
>>> 
>>> .
>>>
>>> Experiment timeline
>>>
>>> Registration opens the week of November 27, 2023.
>>>
>>> The trial will end on December 27, 2024.
>>>
>>> Effective in Chrome versions M120 through M132
>>>
>>> Blink component
>>>
>>> Internals>Network>Cookies
>>> 
>>>
>>> Search tags
>>>
>>> 3pcd 
>>>
>>> TAG review
>>>
>>> None
>>>
>>> TAG review status
>>>
>>> Not applicable
>>>
>>> Risks
>>> Interoperability and Compatibility
>>>
>>> Web Compatibility:
>>>
>>> Despite 3PCs already being blocked in Firefox and Safari and developer
>>> outreach efforts to raise awareness and 

Re: [blink-dev] Request for Deprecation Trial: Deprecate Third-Party Cookies

[Ben Kelly]

The deprecation trial is now open for registrations:

https://developer.chrome.com/origintrials/#/view_trial/3315212275698106369

Again, please be aware this trial will require a review process as outlined
in the blog pos
t.

On Tue, Nov 21, 2023 at 2:53 PM Ben Kelly  wrote:

> FYI, please see this blog post for more information on this deprecation
> trial:
>
> https://developer.chrome.com/blog/third-party-cookie-deprecation-trial/
>
> On Fri, Nov 17, 2023 at 7:52 PM Mike Taylor 
> wrote:
>
>> LGTM for a deprecation trial from M120 to M132. For those of you who have
>> followed my career (all 2 of you), it shouldn't come as a surprise that I
>> appreciate the desire and efforts to minimize the compat implications for
>> sites that are earnestly moving towards this brave new post-3rd-party
>> cookies world.
>>
>> (Note: I don't work on third-party cookie deprecation but I would have
>> landed on a similarly recommended timeline for migration/deprecation.
>> Thanks for being accommodating and realistic to the complicated demands of
>> web development and deployment of different use-cases.)
>>
>> On 11/17/23 1:21 PM, Ben Kelly wrote:
>>
>> Contact emails
>>
>> johann...@chromium.org, wanderv...@chromium.org
>>
>> Explainer
>>
>> None
>>
>> Specification
>>
>>
>> https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-rfc6265bis-12#name-the-cookie-header-field
>>
>> Summary
>>
>> We intend to deprecate and remove default access to third-party (aka
>> cross-site) cookies as part of the Privacy Sandbox Timeline for the Web,
>> starting with an initial 1% testing period in Q1 2024, followed by a
>> gradual phaseout planned to begin in Q3 2024 after consultation with the
>> CMA. (The gradual phaseout is subject to addressing any remaining
>> competition concerns of the UK’s Competition and Markets Authority.)
>>
>> Phasing out third-party cookies (3PCs) is a central effort to the Privacy
>> Sandbox initiative, which aims to responsibly reduce cross-site tracking on
>> the web (and beyond) while supporting key use cases through new
>> technologies. Our phaseout plan was developed with the UK's Competition and
>> Markets Authority, in line with the commitments we offered for Privacy
>> Sandbox for the web.
>>
>> To support this effort we would like to run a deprecation trial for
>> third-party embedded content.  Qualified third-parties participating in the
>> trial can supply a token via an iframe or third-party script in order to
>> continue receiving third-party cookies on requests to that origin.
>>
>> Goals for experimentation
>>
>> The primary goal of the deprecation trial is to reduce the amount of
>> broken user-visible experiences as third-party cookies are phased out.
>> Third-party embedded content or services with these kinds of experiences
>> can use the trial to continue to receive third-party cookies while they
>> work on long term solutions for their users based on CHIPS, Storage Access
>> API, Related Website Sets, FedCM, etc.
>>
>> To meet this goal, requests to register for the deprecation trial will be
>> reviewed to confirm eligibility. Specifically, third-party providers will
>> need to demonstrate functional breakage in user journeys to be eligible.
>> Because the deprecation trial is not intended to support cross-site
>> tracking for advertising purposes, third-party embeds and services used for
>> advertising will not be eligible. The ineligibility of advertising use
>> cases will also help to ensure the deprecation trial does not interfere
>> with the industry testing planned for the start of 2024 as described by
>> the CMA
>> 
>> .
>>
>> Experiment timeline
>>
>> Registration opens the week of November 27, 2023.
>>
>> The trial will end on December 27, 2024.
>>
>> Effective in Chrome versions M120 through M132
>>
>> Blink component
>>
>> Internals>Network>Cookies
>> 
>>
>> Search tags
>>
>> 3pcd 
>>
>> TAG review
>>
>> None
>>
>> TAG review status
>>
>> Not applicable
>>
>> Risks
>> Interoperability and Compatibility
>>
>> Web Compatibility:
>>
>> Despite 3PCs already being blocked in Firefox and Safari and developer
>> outreach efforts to raise awareness and encourage developers to prepare for
>> the deprecation, we currently estimate that a non-trivial number of sites
>> are still relying on third-party cookies for some user-facing
>> functionality. See Intent to Deprecate and Remove for more information:
>> https://groups.google.com/a/chromium.org/g/blink-dev/c/RG0oLYQ0f2I/m/xMSdsEAzBwAJ
>>
>>
>> Interoperability:
>>
>> Both Firefox and Safari have removed default access to third-party
>> cookies already, though there are small differences in how browsers treat
>> 

Re: [blink-dev] Request for Deprecation Trial: Deprecate Third-Party Cookies

[Ben Kelly]

FYI, please see this blog post for more information on this deprecation
trial:

https://developer.chrome.com/blog/third-party-cookie-deprecation-trial/

On Fri, Nov 17, 2023 at 7:52 PM Mike Taylor  wrote:

> LGTM for a deprecation trial from M120 to M132. For those of you who have
> followed my career (all 2 of you), it shouldn't come as a surprise that I
> appreciate the desire and efforts to minimize the compat implications for
> sites that are earnestly moving towards this brave new post-3rd-party
> cookies world.
>
> (Note: I don't work on third-party cookie deprecation but I would have
> landed on a similarly recommended timeline for migration/deprecation.
> Thanks for being accommodating and realistic to the complicated demands of
> web development and deployment of different use-cases.)
>
> On 11/17/23 1:21 PM, Ben Kelly wrote:
>
> Contact emails
>
> johann...@chromium.org, wanderv...@chromium.org
>
> Explainer
>
> None
>
> Specification
>
>
> https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-rfc6265bis-12#name-the-cookie-header-field
>
> Summary
>
> We intend to deprecate and remove default access to third-party (aka
> cross-site) cookies as part of the Privacy Sandbox Timeline for the Web,
> starting with an initial 1% testing period in Q1 2024, followed by a
> gradual phaseout planned to begin in Q3 2024 after consultation with the
> CMA. (The gradual phaseout is subject to addressing any remaining
> competition concerns of the UK’s Competition and Markets Authority.)
>
> Phasing out third-party cookies (3PCs) is a central effort to the Privacy
> Sandbox initiative, which aims to responsibly reduce cross-site tracking on
> the web (and beyond) while supporting key use cases through new
> technologies. Our phaseout plan was developed with the UK's Competition and
> Markets Authority, in line with the commitments we offered for Privacy
> Sandbox for the web.
>
> To support this effort we would like to run a deprecation trial for
> third-party embedded content.  Qualified third-parties participating in the
> trial can supply a token via an iframe or third-party script in order to
> continue receiving third-party cookies on requests to that origin.
>
> Goals for experimentation
>
> The primary goal of the deprecation trial is to reduce the amount of
> broken user-visible experiences as third-party cookies are phased out.
> Third-party embedded content or services with these kinds of experiences
> can use the trial to continue to receive third-party cookies while they
> work on long term solutions for their users based on CHIPS, Storage Access
> API, Related Website Sets, FedCM, etc.
>
> To meet this goal, requests to register for the deprecation trial will be
> reviewed to confirm eligibility. Specifically, third-party providers will
> need to demonstrate functional breakage in user journeys to be eligible.
> Because the deprecation trial is not intended to support cross-site
> tracking for advertising purposes, third-party embeds and services used for
> advertising will not be eligible. The ineligibility of advertising use
> cases will also help to ensure the deprecation trial does not interfere
> with the industry testing planned for the start of 2024 as described by
> the CMA
> 
> .
>
> Experiment timeline
>
> Registration opens the week of November 27, 2023.
>
> The trial will end on December 27, 2024.
>
> Effective in Chrome versions M120 through M132
>
> Blink component
>
> Internals>Network>Cookies
> 
>
> Search tags
>
> 3pcd 
>
> TAG review
>
> None
>
> TAG review status
>
> Not applicable
>
> Risks
> Interoperability and Compatibility
>
> Web Compatibility:
>
> Despite 3PCs already being blocked in Firefox and Safari and developer
> outreach efforts to raise awareness and encourage developers to prepare for
> the deprecation, we currently estimate that a non-trivial number of sites
> are still relying on third-party cookies for some user-facing
> functionality. See Intent to Deprecate and Remove for more information:
> https://groups.google.com/a/chromium.org/g/blink-dev/c/RG0oLYQ0f2I/m/xMSdsEAzBwAJ
>
>
> Interoperability:
>
> Both Firefox and Safari have removed default access to third-party cookies
> already, though there are small differences in how browsers treat
> SameSite=None cookies in so called “ABA” scenarios (site A embeds site B,
> which embeds site A again). Chrome ships the more secure and more
> restrictive variant, and from initial conversations we are optimistic that
> other browsers will adopt it as well. There are also subtle differences in
> how browsers restore access to third-party cookies through mechanisms such
> as heuristics or custom quirks. Where Chrome implements similar measures
> (such as the heuristics), we try to 

Re: [blink-dev] Request for Deprecation Trial: Deprecate Third-Party Cookies

[Mike Taylor]

LGTM for a deprecation trial from M120 to M132. For those of you who 
have followed my career (all 2 of you), it shouldn't come as a surprise 
that I appreciate the desire and efforts to minimize the compat 
implications for sites that are earnestly moving towards this brave new 
post-3rd-party cookies world.


(Note: I don't work on third-party cookie deprecation but I would have 
landed on a similarly recommended timeline for migration/deprecation. 
Thanks for being accommodating and realistic to the complicated demands 
of web development and deployment of different use-cases.)


On 11/17/23 1:21 PM, Ben Kelly wrote:



Contact emails

johann...@chromium.org, wanderv...@chromium.org


Explainer

None


Specification

https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-rfc6265bis-12#name-the-cookie-header-field 




Summary

We intend to deprecate and remove default access to third-party (aka 
cross-site) cookies as part of the Privacy Sandbox Timeline for the 
Web, starting with an initial 1% testing period in Q1 2024, followed 
by a gradual phaseout planned to begin in Q3 2024 after consultation 
with the CMA. (The gradual phaseout is subject to addressing any 
remaining competition concerns of the UK’s Competition and Markets 
Authority.)



Phasing out third-party cookies (3PCs) is a central effort to the 
Privacy Sandbox initiative, which aims to responsibly reduce 
cross-site tracking on the web (and beyond) while supporting key use 
cases through new technologies. Our phaseout plan was developed with 
the UK's Competition and Markets Authority, in line with the 
commitments we offered for Privacy Sandbox for the web.



To support this effort we would like to run a deprecation trial for 
third-party embedded content.  Qualified third-parties participating 
in the trial can supply a token via an iframe or third-party script in 
order to continue receiving third-party cookies on requests to that 
origin.



Goals for experimentation

The primary goal of the deprecation trial is to reduce the amount of 
broken user-visible experiences as third-party cookies are phased 
out.  Third-party embedded content or services with these kinds of 
experiences can use the trial to continue to receive third-party 
cookies while they work on long term solutions for their users based 
on CHIPS, Storage Access API, Related Website Sets, FedCM, etc.



To meet this goal, requests to register for the deprecation trial will 
be reviewed to confirm eligibility. Specifically, third-party 
providers will need to demonstrate functional breakage in user 
journeys to be eligible. Because the deprecation trial is not intended 
to support cross-site tracking for advertising purposes, third-party 
embeds and services used for advertising will not be eligible. The 
ineligibility of advertising use cases will also help to ensure the 
deprecation trial does not interfere with the industry testing planned 
for the start of 2024 as described by the CMA 
.



Experiment timeline

Registration opens the week of November 27, 2023.

The trial will end on December 27, 2024.

Effective in Chrome versions M120 through M132


Blink component

Internals>Network>Cookies 




Search tags

3pcd 


TAG review

None


TAG review status

Not applicable


Risks


Interoperability and Compatibility

Web Compatibility:

Despite 3PCs already being blocked in Firefox and Safari and
developer outreach efforts to raise awareness and encourage
developers to prepare for the deprecation, we currently
estimate that a non-trivial number of sites are still relying
on third-party cookies for some user-facing functionality. See
Intent to Deprecate and Remove for more

information:https://groups.google.com/a/chromium.org/g/blink-dev/c/RG0oLYQ0f2I/m/xMSdsEAzBwAJ




Interoperability:

Both Firefox and Safari have removed default access to third-party 
cookies already, though there are small differences in how browsers 
treat SameSite=None cookies in so called “ABA” scenarios (site A 
embeds site B, which embeds site A again). Chrome ships the more 
secure and more restrictive variant, and from initial conversations we 
are optimistic that other browsers will adopt it as well. There are 
also subtle differences in how browsers restore access to third-party 
cookies through mechanisms such as heuristics or custom quirks. Where 
Chrome implements similar measures (such as the