Five Protected Audience (PA) and Fenced Frames (FF) features were shipped earlier this year but not enabled in the Chrome-facilitated testing Modes A and B <https://developers.google.com/privacy-sandbox/private-advertising/setup/web/chrome-facilitated-testing> to prevent disrupting experiments and measurements during the Chrome-facilitated testing period:
- PA Real Time Reporting (I2S <https://groups.google.com/a/chromium.org/g/blink-dev/c/9_dR-BdyeWE>) - PA multi-bid support (I2S <https://groups.google.com/a/chromium.org/g/blink-dev/c/ZdZXN1D-MtI/>) - PA deprectedReplaceInURN via auction config (I2S <https://groups.google.com/a/chromium.org/g/blink-dev/c/Z9v_94NhDME>) - PA multiple bidding contexts optimization (not web visible) - FF allow cross-origin subframes to send reportEvent() beacons (I2S <https://groups.google.com/a/chromium.org/g/blink-dev/c/CrUxPVSscW0>) With the end of the Chrome-facilitated testing period, we’re going to enable these features in Modes A and B to provide a more consistent developer experience and decrease the need for feature detection. -- 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/CABQTWrnA8B6yHK%3DV6dn7X9g%2BdpEqRx38QLcHq0caYpUwe0sX3g%40mail.gmail.com.
