On Tue, Sep 5, 2023 at 9:55 PM Paul Jensen <pauljen...@chromium.org> wrote:
> Contact emails > > > *pauljen...@chromium.org <pauljen...@chromium.org>*Explainer > > *https://github.com/WICG/turtledove/pull/69 > <https://github.com/WICG/turtledove/pull/695>5* > Can you clarify what this does, as the explainer is not very explain-y? IIUC, the current flow to get directFromSellerSignals is to download a response A which contains a link to a WBN, then download the WBN and that contains the signal info. Your proposal is to change that so that the directFromSellerSignals information would be embedded in a response header on response A? If so, any more details on that header? What would be the header name? What payload sizes should we expect for the header's value? In what conditions will it actually be processed? > > Specification > > > *https://github.com/WICG/turtledove/pull/771 > <https://github.com/WICG/turtledove/pull/771>https://github.com/WICG/turtledove/pull/774 > <https://github.com/WICG/turtledove/pull/774>*Summary > > > *Protected Audience already supports a mechanism to ensure the > authenticity and integrity of information passed into the auction from the > seller called directFromSellerSignals. Currently this is implemented by the > seller providing subresources in a WebBundle to the browser, which after a > year of testing has proved to not be as efficient as originally planned. It > either requires an entirely new additional fetch of a WebBundle, or for the > seller to rewrite and rework an existing fetch to respond instead with only > a WebBundle. This feature is a rewrite of directFromSellerSignals to use an > HTTP response header, transferred via HTTPS same-origin with the seller, > instead of a WebBundle to optimize performance.*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 > <https://github.com/w3ctag/design-reviews/issues/723>*TAG review status > > > *Pending*Risks > > Interoperability and Compatibility > > *None as this is an optional new way of providing > directFromSellerSignals. It cannot be used jointly with the old mechanism, > but there shouldn’t be a need to use the old mechanism.* > > > *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: Adtech asked for this via this Protected Audience Github > issue > <https://github.com/WICG/turtledove/issues/119#issuecomment-1274013176>.* > > > > Debuggability > > > *This feature affects values provided to Protected Audience scripts > (generateBid(), reportResult(), reportWin()) which are debuggable via > Chrome DevTools. This feature also includes console log warnings on parse > failures.*Will this feature be supported on all six Blink platforms > (Windows, Mac, Linux, Chrome OS, 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 add WPTs to cover this API in the next month.*Flag name on > chrome://flags > > > *None*Finch feature name > > > *FledgeDirectFromSellerSignalsHeaderAdSlot*Requires code in //chrome? > > > *False*Estimated milestones > > > *Shipping on desktop and Android in M117.*Anticipated spec changes > > > *None related to this feature.*Link to entry on the Chrome Platform Status > > https://chromestatus.com/feature/5165311598264320 > > 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/CABQTWrkbaAuRoxPUtrQnxyS-W%3DfZjba1JN%2BHCHyLmKCKveHXOg%40mail.gmail.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CABQTWrkbaAuRoxPUtrQnxyS-W%3DfZjba1JN%2BHCHyLmKCKveHXOg%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/CAL5BFfUjzuJiaN4TBpO0a8_6Usn%2BQ0zYYFAVTXuVaH1ZhT-UXg%40mail.gmail.com.
