The I2S messages include details of the specific API functionality for the 115 release, engineering discussions on the proposals, and importantly, the approvals (or LGTMs) from the Blink API owners to ship the feature. As part of the usual process, we’ve sent an "Intent to Ship" (I2S) message to the blink-dev mailing list for each feature.
In the previous post, we introduced the list of relevance and measurement APIs that are launching in Chrome 115. Chrome-facilitated testing modes: Updated details on the options for developers to test the APIs without third-party cookie data.Enrollment: There's an updated enrollment process which is mandatory for developers using the relevance and measurement APIs.Updated user controls: Users will have "Ad privacy" controls to manage the APIs.Ending the unified origin trial: The Privacy Sandbox Relevance and Measurement origin trial ends on Septemproviding overlap with the transition to general availability.
Gradually enabling the APIs: APIs will be gradually enabled over the course of the 115 milestone while monitoring for issues, aiming for 99% availability by mid-August.What's shipping: The launch process for the relevance and measurement APIs: Topics, Protected Audience, Attribution Reporting, Private Aggregation, Shared Storage, and Fenced Frames.In this post, we'll cover the multiple components of this launch, including: That moment is now here, so with Chrome 115 going to Stable, we are beginning the process of gradually enabling the APIs in the next few days. In May we shared our plans to ship the Privacy Sandbox relevance and measurement APIs in Chrome 115.
0 kommentar(er)
