Hey all, This may be overfitting against my personal priors, but I'm *intensely *skeptical of any web platform API addition that claims to be "temporary". If we want a temporary mechanism, we can use OTs and set a date-certain for removal and prevent over-use that would back us into a corner.
Without some sort of guardrail, I'm not optimistic that we'll be able to actually get rid of a useful debugging aid that is web-exposed. Can we reformulate this as an OT? Or is the team proposing this willing to document a more thorough plan for deprecation and removal, perhaps including reporting of use (via UMA histograms)? Best, Alex On Wednesday, March 6, 2024 at 7:49:16 AM UTC-8 Mike Taylor wrote: > LGTM2 > On 3/6/24 5:39 AM, Yoav Weiss (@Shopify) wrote: > > LGTM1 > > On Thu, Feb 29, 2024 at 7:29 PM Alex Turner <[email protected]> wrote: > >> Contact emails [email protected] >> >> Explainer >> https://github.com/WICG/turtledove/blob/main/FLEDGE_extended_PA_reporting.md#temporary-debugging-mechanism >> >> Specification >> https://github.com/patcg-individual-drafts/private-aggregation-api/pull/118 >> >> Summary >> >> Adds support for Private Aggregation’s debug mode for the per-buyer >> extended Private Aggregation reporting to Protected Audience sellers (aka >> auctionReportBuyers reporting). This is done with a new, optional >> auctionReportBuyerDebugModeConfig field passed to runAdAuction(). >> auctionReportBuyers reporting is currently the only use of Private >> Aggregation reports that does not have a way to enable its debug mode (a >> temporary mechanism tied to third-party cookie eligibility that relaxes >> some of the API’s privacy constraints to allow for easier debugging and >> integration). >> >> >> Blink component Blink>PrivateAggregation >> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EPrivateAggregation> >> >> TAG review https://github.com/w3ctag/design-reviews/issues/846 (We have >> not requested a signal for these changes specifically.) >> >> TAG review status Pending >> >> Risks >> >> >> Interoperability and Compatibility >> >> This feature is optional and backwards compatible. >> >> >> *Gecko*: No signal ( >> https://github.com/mozilla/standards-positions/issues/805) We have not >> requested a signal for this change specifically. >> >> *WebKit*: No signal ( >> https://github.com/WebKit/standards-positions/issues/189) We have not >> requested a signal for this change specifically. >> >> *Web developers*: Positive (https://github.com/WICG/turtledove/issues/709) >> This has been requested by developers. >> >> *Other signals*: >> >> WebView application risks >> >> Does this intent deprecate or change behavior of existing APIs, such that >> it has potentially high risk for Android WebView-based applications? >> >> None >> >> >> Debuggability >> >> This is primarily a debugging feature -- allowing the existing debug mode >> for this kind of Private Aggregation reporting. >> >> >> Will this feature be supported on all six Blink platforms (Windows, Mac, >> Linux, ChromeOS, Android, and Android WebView)? >> >> 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 >> >> Flag name on chrome://flags None >> >> Finch feature name PrivateAggregationAuctionReportBuyerDebugModeConfig >> >> Requires code in //chrome? False >> >> Tracking bug https://crbug.com/1513013 >> >> Launch bug https://launch.corp.google.com/launch/4302460 >> >> Estimated milestones >> >> We’re aiming to ship in M123. >> >> Anticipated spec changes >> >> None >> >> Link to entry on the Chrome Platform Status >> https://chromestatus.com/feature/5088927692357632 >> >> 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 [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAA%2BBiFkYb%3DWswXSKM%2B9ESFdgTBUdbjoDq21Q5sWJm%2BPWqqE_nw%40mail.gmail.com >> >> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAA%2BBiFkYb%3DWswXSKM%2B9ESFdgTBUdbjoDq21Q5sWJm%2BPWqqE_nw%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 [email protected]. > > To view this discussion on the web visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOmohS%2BJt8bhfgO5iLVa7j3byo%2Bov8%3D_kh-Jt6hLfBEbWyJHPA%40mail.gmail.com > > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOmohS%2BJt8bhfgO5iLVa7j3byo%2Bov8%3D_kh-Jt6hLfBEbWyJHPA%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 [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/3f3357ba-54b9-4589-9559-f49614db5148n%40chromium.org.
