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 over reportEvent()
>> beacons
). 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:
>
>> On 5/8/24 11:30 AM, 'Liam Brady
cted 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...@chromium.org
>
> Explainer(s)
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
he 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:
>
> Contact emails
>
&g
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
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
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 All Registered Destinatio
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
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)
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 Beacons To All
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)
acro 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> wrote:
>
>> Contact emails
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,
14 matches
Mail list logo
