We then intend to increase availability to approximately 60% of browsers at the start of August. Overall percentages of Chrome browsers may also not map to the same percentage of an individual site's traffic, so you should only use this as indicative of expected traffic. All percentages shown are approximate and developers should expect fluctuations in this period as we may adjust levels to respond to issues. Users need to relaunch Chrome before version updates or incremental API updates take effect, meaning it always takes additional time for the ramp up to reach the target levels. These isolated groups provide a quicker route for identifying potential issues with the APIs. Similar to the unified origin trial, this ramp-up will include a main group with all APIs enabled and several smaller isolated groups with a subset of APIs enabled. Then we intend to ramp up to enabling the APIs for approximately 35% of browsers over about a week. Our aim is to start this process a few days after the 115 Stable date of July 18, 2023, most likely the week of July 24. # Gradually enabling APIsĪs with some previous Privacy Sandbox features, we'll gradually enable the relevance and measurement APIs for an increasing percentage of browser instances to make sure that we can monitor and respond to any potential issues. Additionally, we're in the process of gradually enabling First-Party Sets ( I2S), Private State Tokens ( I2S), and will be shipping Storage Partitioning ( I2S). You can check out the I2S messages for Attribution Reporting API, Protected Audience, Topics API, Private Aggregation API, Shared Storage API, and Fenced Frames.Īlongside the web platform APIs, the Aggregation Service for Attribution Reporting and Private Aggregation is also moving to general availability. 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |