Contact emails shivani...@chromium.org d...@chromium.org jkar...@chromium.org lbr...@google.com Explainer(s)
Send Automatic Beacons To All Registered Destinations https://github.com/WICG/turtledove/pull/808 Spec(s) Send Automatic Beacons To All Registered Destinations (Initial version) https://github.com/WICG/fenced-frame/pull/122 (Post-security review updates) https://github.com/WICG/fenced-frame/pull/129 Summary We launched Fenced Frames as a part of Chrome 115. One of its capabilities is being able to send reporting beacons automatically after a top-level navigation. We would like to modify that functionality: Automatic beacons will now send to all registered URLs. Previously, only destinations specified when calling setReportEventDataForAutomaticBeacons() receive automatic beacons, even if that destination called registerAdBeacon() for "reserved.top_navigation" in their worklet. Now, any destination that called registerAdBeacon() for "reserved.top_navigation" will get an automatic beacon, but only destinations specified in setReportEventDataForAutomaticBeacons() will get automatic beacon data along with the beacon. setReportEventDataForAutomaticBeacons() still must be invoked before automatic beacons can send out, effectively making the function a way for the frame’s origin to opt in to automatic beacons. Note: This chromestatus entry also includes changes to Protected Audience ad size macros. However, it is small enough that it will be taken care of in a separate PSA: https://groups.google.com/a/chromium.org/g/blink-dev/c/3JfA8EUBEgQ Blink component Blink>FencedFrames <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EFencedFrames> TAG reviews and status Fenced frames existing TAG review appended with these spec changes https://github.com/w3ctag/design-reviews/issues/838#issuecomment-1765061770 Link to Origin Trial feedback summary No Origin Trial performed Is this feature supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)? Supported on all the above platforms except Android WebView. Debuggability Additional debugging capabilities are not necessary for these feature changes. Risks Compatibility There are no compatibility risks, as described below: The API shape as exposed to ad frames is not changing. While the assumptions of which sites receive the beacon after calling setReportEventDataForAutomaticBeacons() is changing, no code changes will be required to have existing code work with this new behavior. Interoperability there are no interoperability risks as no other browsers have decided to implement these features yet. Is this feature fully tested by web-platform-tests <https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md>? Link to test suite results from wpt.fyi. Yes automatic-beacon-no-destination.https.html (test <https://github.com/web-platform-tests/wpt/blob/master/fenced-frame/automatic-beacon-no-destination.https.html>) (results <https://wpt.fyi/results/fenced-frame/automatic-beacon-no-destination.https.html?label=experimental&label=master&aligned> ) automatic-beacon-no-opt-in.https.html (test <https://github.com/web-platform-tests/wpt/blob/master/fenced-frame/automatic-beacon-no-opt-in.https.html>) (results <https://wpt.fyi/results/fenced-frame/automatic-beacon-no-opt-in.https.html?label=experimental&label=master&aligned> ) Anticipated spec changes None Link to entry on the Chrome Platform Status https://chromestatus.com/feature/5140606359175168 Links to previous Intent discussions Intent to prototype: https://groups.google.com/a/chromium.org/g/blink-dev/c/Ko9UXQYPgUE/m/URRsB-qvAAAJ Intent to experiment: https://groups.google.com/a/chromium.org/g/blink-dev/c/y6G3cvKXjlg/m/Lcpmpi_LAgAJ Intent to extend origin trial: https://groups.google.com/a/chromium.org/g/blink-dev/c/SD8Ot2gpz4g/m/A9uA-_cGAwAJ https://groups.google.com/a/chromium.org/g/blink-dev/c/gpmaOi3of_w/m/SyMclFhMAAAJ https://groups.google.com/a/chromium.org/g/blink-dev/c/CBrV-2DrYFI/m/RTojC6kHAgAJ Intent to ship: https://groups.google.com/a/chromium.org/g/blink-dev/c/tpw8wW0VenQ/m/mePLTiHlDQAJ Intent to ship for functionality updates: https://groups.google.com/a/chromium.org/g/blink-dev/c/2FKlwNZ0J4Q/m/oQmHtp1rAQAJ -- 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 on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/8c564532-be09-4d4a-8801-8292cba18240n%40chromium.org.
