LGTM On Tue, Jul 22, 2025 at 11:33 AM Nan Lin <lin...@chromium.org> wrote:
> Contact emails > > lin...@chromium.org, jkar...@chromium.org > > Explainer > > > https://github.com/privacysandbox/tpcd-labeling/blob/main/cookie_deprecation_labeling_explainer.md > > https://developer.chrome.com/en/docs/privacy-sandbox/chrome-testing > > Summary > > The cookie deprecation labels are useful for developers to evaluate and > optimize deployments of the Privacy Sandbox APIs, and we want to avoid > disruption while we engage with the industry to gather feedback on an > updated roadmap for these technologies. Therefore we are asking to extend > the current set of labels > <https://developers.google.com/privacy-sandbox/relevance/setup/web/chrome-facilitated-testing> > for three more milestones. > > > Link to “Intent to Experiment” blink-dev discussion > > > https://groups.google.com/a/chromium.org/g/blink-dev/c/NJrU4AQ5m_I/m/l-SaSj9MEQAJ > > > > Goals for experimentation > > Continued deployment and evaluation of Privacy Sandbox Ads APIs. > > Experimental timeline > > This feature was previously approved to run up until Chrome 138. > > We would like to extend this for Chrome 139 through 141, inclusive. > > Any risks when the experiment finishes? > > Minimal, the cookie deprecation labels are only available for a subset of > users and must be requested. Embedded services that will need to detect > third-party cookie availability in Chrome > <https://privacysandbox.google.com/cookies/prepare/detect> after the > experiment ends can utilize Storage Access Headers > <https://github.com/privacycg/storage-access-headers> instead of relying > on these labels. > > As new clients are ineligible for the experiment, the percentage of > clients that receive the labels will decay over time, and eventually the > experiment will effectively expire naturally. > > Reason this experiment is being extended > > We have received feedback that these labels are useful for ad tech > companies to evaluate and optimize the APIs, and we want to avoid > disruption while we engage with the industry to gather feedback on an > updated roadmap for these technologies. > > Ongoing technical constraints > > None > > Will this feature be supported on all five Blink platforms supported by > Origin Trials (Windows, Mac, Linux, Chrome OS, and Android)? > > No, not supported on webview. > > Link to entry on the feature dashboard > > https://chromestatus.com/feature/5189079788683264 > > -- > 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 visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CA%2BVrgPnPr4niRt-QVnBd8VsaD1uZAd3VQEKzB0XXeR2CHpbD7g%40mail.gmail.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CA%2BVrgPnPr4niRt-QVnBd8VsaD1uZAd3VQEKzB0XXeR2CHpbD7g%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- 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 visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFUtAY9zdLKYS8B3TSCC3%2B4CV0o4qdUEcSfdT7gKF6ytPB4w3w%40mail.gmail.com.
