[blink-dev] Intent to Ship: Fenced Frames - Functionality Updates

Contact emails shivani...@chromium.org, d...@chromium.org, jkar...@chromium.org, lbr...@google.com Explainer(s) Send Automatic Beacons Once https://github.com/WICG/turtledove/pull/718 Serializable Fenced Frames Configs - Minor Change, No explainer available. Note: With this change, FencedFr

Re: [blink-dev] Intent to Ship: Fenced Frames - Functionality Updates

Is the entity that sets the macro values always the same that has set > the patterns the values are being used for, or could those be different > entities? > > Thanks! > > > On Fri, Aug 25, 2023 at 9:34 PM 'Liam Brady' via blink-dev < > blin...@chromium.org

[blink-dev] Intent to Ship: Fenced Frame - Functionality Updates

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) htt

Re: [blink-dev] Intent to Ship: Fenced Frame - Functionality Updates

t 16, 2023 at 9:42 PM 'Liam Brady' via blink-dev < > blink-dev@chromium.org> wrote: > >> Contact emails >> >> shivani...@chromium.org d...@chromium.org jkar...@chromium.org >> lbr...@google.com >> Explainer(s) >> >> Send Automatic Beaco

[blink-dev] Intent to Ship: Fenced Frame - Functionality Updates

Contact emails shivani...@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/WIC

[blink-dev] Re: Intent to Ship: Fenced Frame - Functionality Updates

Just requested the reviews. On Wed, Oct 25, 2023 at 11:21 AM Yoav Weiss wrote: > Can you kick off the review on the 5 other review categories in the > chromestatus entry? > > On Friday, October 20, 2023 at 10:37:37 PM UTC+2 blink-dev wrote: > >> Contact emails >> >> shivani...@chromium.org jkar.

Re: [blink-dev] Intent to Ship: Fenced Frame - Functionality Updates

am On Wed, Oct 25, 2023 at 7:44 PM Mike Taylor wrote: > Hi Liam! > > On 10/20/23 4:37 PM, 'Liam Brady' via blink-dev wrote: > > Contact emails > > shivani...@chromium.org jkar...@chromium.org lbr...@google.com > Explainer(s) > > Send Automatic Beacons To

[blink-dev] Intent to Ship: Fenced Frames - Enable Leaving IGs, and Ads Report at Top Level Navigation Start (Chrome - 120)

Contact emails shivani...@chromium.org, jkar...@chromium.org, lbr...@google.com, xiaoche...@google.com Explainer(s) Enable Leaving Ad Interest Groups from Urn iFrames and Ad Component Frames https://github.com/WICG/turtledove/pull/879 https://github.com/WICG/turtledove/blob/11d500c87bb39

[blink-dev] Intent to Ship: Allow Cross-Origin Subframes to Send Automatic Beacons

Contact emails lbr...@google.com, shivani...@chromium.org, jkar...@chromium.org Explainer(s) https://github.com/WICG/turtledove/pull/904 Spec(s) https://github.com/WICG/fenced-frame/pull/133 Summary As part of the Privacy Sandbox experiment, we introduced a way for beacons to be sent auto

Re: [blink-dev] Intent to Ship: Allow Cross-Origin Subframes to Send Automatic Beacons

on the frame's behalf), and since permissions policies are based on inheritance, that was something we needed to avoid. On Friday, January 19, 2024 at 3:43:44 PM UTC-5 mike...@chromium.org wrote: > Hi Liam, > On 1/16/24 3:49 PM, 'Liam Brady' via blink-dev wrote: > > Co

[blink-dev] Intent to Ship: Protected Audience ads reporting - allow cross-origin subframes to send reportEvent() beacons

Contact emails lbr...@google.com, shivani...@chromium.org, jkar...@chromium.org Explainer(s) https://github.com/WICG/turtledove/pull/1134 Spec(s) https://github.com/WICG/fenced-frame/pull/152 Summary Ad frames (both fenced frames and urn-iframes) created through a Protected Audience aucti

Re: [blink-dev] Intent to Ship: Protected Audience ads reporting - allow cross-origin subframes to send reportEvent() beacons

of the overall Protected Audience API, and this feature doesn't change that. On Wed, May 8, 2024 at 1:27 PM Mike Taylor wrote: > On 5/8/24 11:30 AM, 'Liam Brady' via blink-dev wrote: > > Contact emails > > lbr...@google.com, shivani...@chromium.org, jkar...@

Re: [blink-dev] Intent to Ship: Protected Audience ads reporting - allow cross-origin subframes to send reportEvent() beacons

he buyer/advertisers). The > first-party (i.e. the publishers) don't have control over reportEvent() > beacons since that is considered part of the overall Protected Audience > API, and this feature doesn't change that. > > On Wed, May 8, 2024 at 1:27 PM Mike Taylor wrote: >

Re: [blink-dev] Intent to Ship: Protected Audience ads reporting - allow cross-origin subframes to send reportEvent() beacons

>> beacons rests within the worklet owner that invokes >> registerAdBeacon()/registerAdMacro() i.e. seller/ buyer and the document >> loaded with the main ad renderURL (i.e. the buyer/advertisers). The >> first-party (i.e. the publishers) don't have control ov

[blink-dev] Intent to ship: Send "Referer" header in reportEvent/automatic beacons

Contact emails lbr...@google.com, shivani...@chromium.org, jkar...@chromium.org Specification https://github.com/WICG/fenced-frame/pull/164 Summary Reporting beacons (e.g. reportEvent to preregistered destination URLs

Re: [blink-dev] Intent to ship: Send "Referer" header in reportEvent/automatic beacons

..@chromium.org wrote: > One other request: can you please request enterprise, debuggability, and > test bits in your chromestatus entry? > On 12/2/24 9:51 AM, Mike Taylor wrote: > > On 11/28/24 6:41 AM, 'Liam Brady' via blink-dev wrote: > > Contact emails

[blink-dev] Intent to ship: Automatic beacon cross-origin data support (M135)

Contact emails lbr...@google.com, shivani...@chromium.org, jkar...@chromium.org Explainer https://github.com/WICG/turtledove/pull/1386 Specification https://github.com/WICG/fenced-frame/pull/203 Summary This change allows descendant documents of fenced frames to set the root fenced frame’s

Re: [blink-dev] Intent to ship: Automatic beacon cross-origin data support (M135)

g then. Note that these tests are all passing on the Chromium build bots where the feature is turned on. On Monday, March 24, 2025 at 9:54:40 AM UTC-4 mike...@chromium.org wrote: > On 3/19/25 1:16 PM, 'Liam Brady' via blink-dev wrote: > > Contact emails > > lbr...@google

Re: [blink-dev] Intent to ship: Automatic beacon cross-origin data support (M135)

d > frames with local unpartitioned data access > <https://chromestatus.com/feature/5072963051454464>, and the tests should > start passing then. Note that these tests are all passing on the Chromium > build bots where the feature is turned on. > > Makes sense, tha

Re: [blink-dev] Intent to ship: Automatic beacon cross-origin data support (M135)

> There's a bit of an overloaded terminology that confuses me: when you refer to a cross-origin subframe, are we talking about a cross-origin fenced frame or an iframe? My recollection is that in a fenced frame case, one cannot use postMessage to communicate with its embedder. Having this data