LGTM3 On Tuesday, April 1, 2025 at 3:51:41 PM UTC-4 beham...@google.com wrote:
> Can I get an update on this? > > Thanks, > --Benjamin "Russ" Hamilton > > On Wed, Mar 26, 2025 at 12:56 PM Mike Taylor <miketa...@chromium.org> > wrote: > >> LGTM2 >> On 3/26/25 11:56 AM, 'Russ Hamilton' via blink-dev wrote: >> >> Yes, it's just a performance/ergonomics change. Developers could >> previously get the same effect by calling the existing API multiple times. >> >> On Wed, Mar 26, 2025 at 11:35 AM Chris Harrelson <chris...@chromium.org> >> wrote: >> >>> Sounds fine - a performance and ergonomics optimization for developers >>> only, right? >>> >>> LGTM1 >>> >>> On Tue, Mar 25, 2025 at 12:01 PM 'Russ Hamilton' via blink-dev < >>> blink-dev@chromium.org> wrote: >>> >>>> Explainer >>>> >>>> >>>> https://github.com/WICG/turtledove/blob/main/FLEDGE_browser_bidding_and_auction_API.md#device-orchestrated-multi-seller-auctions >>>> >>>> >>>> https://github.com/WICG/turtledove/pull/1403 >>>> >>>> Specification >>>> >>>> https://wicg.github.io/turtledove/#getInterestGroupAdAuctionData >>>> >>>> https://github.com/WICG/turtledove/pull/1389 >>>> >>>> Summary >>>> >>>> Add support for navigator.getInterestGroupAdAuctionData to return the >>>> encrypted B&A request payload for multiple sellers in a single call. This >>>> allows multiple sellers sharing a single piece of on-page JavaScript to >>>> more efficiently run Protected Audience advertisement selection auctions. >>>> >>>> Blink component >>>> >>>> Blink>InterestGroups >>>> <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EInterestGroups%22> >>>> >>>> TAG review >>>> >>>> For Protected Audience Bidding and Auction Services: >>>> https://github.com/w3ctag/design-reviews/issues/1009 >>>> >>>> For Protected Audience: >>>> https://github.com/w3ctag/design-reviews/issues/723 >>>> >>>> TAG review status >>>> >>>> Completed for Protected Audience Bidding and Auction Services, declined. >>>> >>>> Completed for Protected Audience, resolved unsatisfied. >>>> >>>> Risks Interoperability and Compatibility >>>> >>>> Optional new functionality that does not break existing use. >>>> >>>> Gecko & WebKit: Negative >>>> <https://github.com/mozilla/standards-positions/issues/770#issuecomment-2432124085> >>>> >>>> from Mozilla for the parent proposal, Protected Audience Bidding and >>>> Auction Services. No signal >>>> <https://github.com/WebKit/standards-positions/issues/158#issuecomment-2432121278> >>>> >>>> from Webkit on parent proposal, Protected Audience Bidding and Auction >>>> Services. >>>> >>>> Edge: Edge is running an Origin Trial of the Ad Selection API >>>> <https://github.com/WICG/privacy-preserving-ads/blob/main/README.md> >>>> which shares a Web API and services protocol with Protected Audience and >>>> will also benefit from this extension. >>>> >>>> Web developers: Requested here >>>> <https://github.com/prebid/Prebid.js/issues/12456> >>>> >>>> WebView application risks >>>> >>>> Protected Audience not available in WebView >>>> >>>> Debuggability >>>> >>>> API is debuggable in DevTools - developers can step over the API call >>>> and see the results. >>>> >>>> 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> >>>> ? >>>> >>>> Yes >>>> <http://github.com/web-platform-tests/wpt/blob/master/fledge/tentative/get-interest-group-auction-data.https.window.js#L625> >>>> >>>> Flag name on about://flags >>>> >>>> None >>>> >>>> Finch feature name >>>> >>>> FledgeBiddingAndAuctionServerAPIMultiSeller >>>> >>>> Requires code in //chrome? >>>> >>>> False >>>> >>>> Estimated milestones >>>> >>>> Shipping on desktop >>>> >>>> 134 >>>> >>>> Shipping on Android >>>> >>>> 134 >>>> >>>> >>>> Anticipated spec changes >>>> >>>> No anticipated spec changes. >>>> >>>> Link to entry on the Chrome Platform Status >>>> >>>> https://chromestatus.com/feature/5167187989626880?gate=5069253138710528 >>>> >>>> -- >>>> 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/CAAG-DU0J995_2-uyb%2B1fjMwu5kWRW0kO1m0BJyL_Jk%2BJ%2BE1F0A%40mail.gmail.com >>>> >>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAAG-DU0J995_2-uyb%2B1fjMwu5kWRW0kO1m0BJyL_Jk%2BJ%2BE1F0A%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 visit >> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAAG-DU2EoWm0WFAPgWJruH1maGt%2BzFfRGZAbPzL1w0OdjZCXDg%40mail.gmail.com >> >> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAAG-DU2EoWm0WFAPgWJruH1maGt%2BzFfRGZAbPzL1w0OdjZCXDg%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 visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/199f1c15-bec5-453f-a60d-33ac8098b5fen%40chromium.org.
