Great, thank you! Yep, looks like the PR is about to land to me, I'm satisfied. LGTM1
On Wed, Jan 24, 2024 at 10:02 AM Paul Jensen <pauljen...@chromium.org> wrote: > That spec PR has now been reviewed and approved by the Protected > Audience team and our spec mentor. Once a couple nits are addressed, I > imagine it'll land shortly. > > On Wed, Jan 10, 2024 at 10:24 AM Rick Byers <rby...@chromium.org> wrote: > >> Hi Paul, >> This looks like a minor addition to me. My only concern is that this >> spec PR <https://github.com/WICG/turtledove/pull/954> hasn't been >> reviewed yet, and we generally prefer for all tests to land before >> approval. Would it be reasonable to get those done before we approve this? >> >> Thanks, >> Rick >> >> >> >> On Fri, Jan 5, 2024 at 1:05 PM Paul Jensen <pauljen...@chromium.org> >> wrote: >> >>> Contact emails >>> >>> pauljen...@chromium.org >>> >>> >>> Explainer >>> >>> Ad slot size in real-time bidding signals fetch: >>> https://github.com/WICG/turtledove/pull/928 >>> >>> Update more interest group fields: Already covered by explainer >>> <https://github.com/WICG/turtledove/blob/main/FLEDGE.md#:~:text=any%20new%20values%20returned%20in%20this%20way%20overwrite%20the%20values%20previously%20stored%20(except%20that%20the%20name%20and%20owner%20cannot%20be%20changed> >>> >>> >>> Specification >>> >>> Ad slot size in real-time bidding signals fetch: >>> https://github.com/WICG/turtledove/pull/954 >>> >>> Update more interest group fields: >>> https://github.com/WICG/turtledove/pull/907 >>> https://github.com/WICG/turtledove/pull/953 >>> >>> >>> Summary >>> >>> Ad slot size in real-time bidding signals fetch: >>> >>> Protected Audience ad selection auctions allow buyers to fetch real-time >>> signals from their key-value server. Besides being used for calculating >>> bid prices, these signals can also be used for prioritizing and filtering >>> potential ad candidates. The more ad candidate filtration and >>> prioritization that we can enable, the more performant the auction is (e.g. >>> less browser resource utilization) and the higher the quality of the chosen >>> ad candidates is. This feature extends the signals about the page where >>> the ad will be displayed from just its domain name, to also include the >>> size of the ad slots on the page, which is a very useful signal for >>> filtering out ads that cannot be rendered in that slot size. >>> >>> Allow updating interest group’s userBiddingSignals and executionMode: >>> >>> Protected Audience has always supported updating interest group fields, >>> but for historical reasons did not support updating the interest group >>> field named userBiddingSignals, and for no obvious reason did not support >>> updating executionMode. This change is a small extension to Protected >>> Audience interest group updating to support updating these fields, making >>> the API more useful by being able to update/refresh the fields with more up >>> to date information. >>> >>> >>> Blink component >>> >>> Blink>InterestGroups >>> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EInterestGroups> >>> >>> >>> TAG review >>> >>> The parent proposal, Protected Audience, is still pending: >>> https://github.com/w3ctag/design-reviews/issues/723 >>> >>> >>> TAG review status >>> >>> Pending >>> >>> >>> Risks >>> >>> >>> Interoperability and Compatibility >>> >>> These are both optional new features so we do not expect them to cause >>> compatibility breakage. >>> >>> >>> Gecko & WebKit: No signal on parent proposal, Protected Audience. >>> Asked in the Mozilla forum here >>> <https://github.com/mozilla/standards-positions/issues/770>, and in the >>> Webkit forum here >>> <https://github.com/WebKit/standards-positions/issues/158>. >>> >>> >>> Web developers: >>> >>> Ad slot size in real-time bidding signals fetch: Interest from multiple >>> adtechs here <https://github.com/WICG/turtledove/issues/869>. >>> >>> Update more interest group fields: Interest from adtech here >>> <https://github.com/WICG/turtledove/issues/760>. >>> >>> >>> Debuggability >>> >>> Ad slot size in real-time bidding signals fetch: The extra >>> runAdAuction() and joinAdInterestGroup() parameters should be visible in >>> DevTools, as should the real-time bidding signal fetches in the DevTools >>> network panel. >>> >>> Update more interest group fields: The updates should be visible in >>> DevTools’ Application Storage Interest Group section. >>> >>> >>> Will this feature be supported on all six Blink platforms (Windows, Mac, >>> Linux, ChromeOS, Android, and Android WebView)? >>> >>> It will be supported on all platforms that support Protected Audience, >>> so all but WebView. >>> >>> >>> Is this feature fully tested by web-platform-tests >>> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> >>> ? >>> >>> We plan to land web-platform-tests for both features shortly. Some >>> have already landed >>> <https://chromium-review.googlesource.com/c/chromium/src/+/5077540/17/third_party/blink/web_tests/external/wpt/fledge/tentative/trusted-bidding-signals.https.window.js> >>> . >>> >>> >>> Flag name on chrome://flags >>> >>> None >>> >>> >>> Finch feature name >>> >>> EnableIFrameAdAuctionHeaders, >>> EnableUpdatingExecutionModeToFrozenContext, EnableUpdatingUserBiddingSignals >>> >>> >>> Requires code in //chrome? >>> >>> False >>> >>> >>> Estimated milestones >>> >>> Shipping on desktop and Android in M121. >>> >>> Anticipated spec changes >>> >>> None related to these features. >>> >>> >>> Link to entry on the Chrome Platform Status >>> >>> https://chromestatus.com/feature/5090856430469120 >>> >>> >>> This intent message was generated by Chrome Platform Status >>> <https://chromestatus.com/>. >>> >>> -- >>> 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/CABQTWrm0w3XL4%3DKyEu4ESkJBg2cfah%3D4bdwt%3DJU9tLjo1mEQww%40mail.gmail.com >>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CABQTWrm0w3XL4%3DKyEu4ESkJBg2cfah%3D4bdwt%3DJU9tLjo1mEQww%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 on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFUtAY-q4PO%2BmxGa8OZs%3D0V9z3eHr%2B269nEEVqOfmBFpPv20fg%40mail.gmail.com.
