Hi Akash - the Attribution Reporting API is supported in Android WebView, why won't these extensions be?
Thanks, Peter On Thu, Feb 22, 2024 at 8:32 PM 'Akash Nadan' via blink-dev < blink-dev@chromium.org> wrote: > Hi All, > > We did not do an OT for these features. But we have discussed and > collected feedback regarding these features with multiple ad-techs and have > shared these features during the WICG (web platform incubator community > group) weekly calls. > > Thanks, > Akash > > On Wednesday, February 21, 2024 at 8:57:48 AM UTC-8 Alex Russell wrote: > >> Hey folks, >> >> I also appreciate the quality of the design work here, but we need >> developer interest to be able to launch features out ahead of other >> engines. Was an OT done? What other signals do we have to go on? >> >> Best, >> >> Alex >> >> On Tuesday, February 20, 2024 at 10:56:21 PM UTC-8 Yoav Weiss wrote: >> >>> LGTM2 >>> >>> On Wednesday, February 21, 2024 at 6:02:29 AM UTC+1 Domenic Denicola >>> wrote: >>> >>>> LGTM1. I appreciate the detailed explainers and well-reviewed spec >>>> updates. >>>> >>>> I noticed the TAG review field was missing, but it seems the TAG review >>>> for the base feature is still ongoing >>>> <https://github.com/w3ctag/design-reviews/issues/724> since >>>> 2022-03-24, so I agree with the decision to not derailing that ongoing >>>> review by requesting additional review for small additions like this. >>>> >>>> On Tuesday, February 13, 2024 at 3:12:22 AM UTC+9 Akash Nadan wrote: >>>> >>>>> Contact emails >>>>> >>>>> akash...@google.com, lin...@chromium.org, john...@chromium.org >>>>> >>>>> Explainer >>>>> >>>>> Attribution Reporting with event-level reports >>>>> <https://github.com/WICG/attribution-reporting-api/blob/main/EVENT.md> >>>>> >>>>> Attribution Reporting API with Aggregatable Reports >>>>> <https://github.com/WICG/attribution-reporting-api/blob/main/AGGREGATE.md> >>>>> >>>>> Aggregation Service for the Attribution Reporting API >>>>> <https://github.com/WICG/attribution-reporting-api/blob/main/AGGREGATION_SERVICE_TEE.md> >>>>> >>>>> Specification >>>>> >>>>> https://wicg.github.io/attribution-reporting-api/ >>>>> >>>>> Blink component >>>>> >>>>> Internals > AttributionReporting >>>>> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Internals%3EAttributionReporting> >>>>> >>>>> Summary >>>>> >>>>> We plan on landing the following changes to the Attribution Reporting >>>>> API focused on: >>>>> >>>>> - >>>>> >>>>> additional API configurability for event-level reporting by >>>>> supporting customization for trigger data cardinality and values >>>>> - >>>>> >>>>> additional API configurability for summary reports by supporting >>>>> filters in aggregatable values >>>>> >>>>> >>>>> Explainer/Spec changes >>>>> >>>>> - Allow sources to customize trigger data cardinality and values >>>>> <https://github.com/WICG/attribution-reporting-api/pull/1129> >>>>> - Allow trigger side filtering on aggregation keys >>>>> <https://github.com/WICG/attribution-reporting-api/pull/1149> >>>>> >>>>> >>>>> Risks >>>>> Interoperability and Compatibility >>>>> >>>>> Both features are fully backwards compatible changes and are optional >>>>> features. >>>>> >>>>> >>>>> Will this feature be supported on all six Blink platforms (Windows, >>>>> Mac, Linux, Chrome OS, Android, and Android WebView)? >>>>> >>>>> All except Android WebView >>>>> >>>>> Is this feature fully tested by web-platform-tests >>>>> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> >>>>> ? >>>>> >>>>> Yes >>>>> >>>>> Estimated milestones >>>>> >>>>> Chrome 123 >>>>> >>>>> Link to entry on the Chrome Platform Status >>>>> >>>>> https://chromestatus.com/feature/5170344510095360 >>>>> >>>>> Links to previous Intent discussions >>>>> >>>>> Previous I2S: >>>>> >>>>> Intent to Ship: Attribution Reporting API >>>>> <https://groups.google.com/a/chromium.org/g/blink-dev/c/2Rmj5V6FSaY> >>>>> >>>>> Intent to Ship: Attribution Reporting features M117 >>>>> <https://groups.google.com/a/chromium.org/g/blink-dev/c/nWF61c8xu-M/m/uMmH1ewcAQAJ> >>>>> >>>>> Intent to Ship: Attribution Reporting features M118 >>>>> <https://groups.google.com/a/chromium.org/g/blink-dev/c/Mh-mJiyJZFk/m/HlgzpphYBQAJ> >>>>> >>>>> Intent to Ship: Attribution Reporting features M119 >>>>> <https://groups.google.com/a/chromium.org/g/blink-dev/c/6e44SBtEtcQ> >>>>> >>>>> Intent to Ship: Attribution Reporting features M120 >>>>> <https://groups.google.com/a/chromium.org/g/blink-dev/c/jSk3xpNPzGQ/m/VZPsdYgGCAAJ> >>>>> >>>>> Intent to Ship: Attribution Reporting features M121 >>>>> <https://groups.google.com/a/chromium.org/g/blink-dev/c/g9KiC6Rg_mA/m/V679WcWuAQAJ> >>>>> >>>>> -- > 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/cb63f3a9-0856-4387-8e5b-1a2281d60409n%40chromium.org > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/cb63f3a9-0856-4387-8e5b-1a2281d60409n%40chromium.org?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/CALt3x6n-qpQ5Lg4pPALdwA%2BK%3DsJ3FJhggKm2s1BXr%2BxWeuDTyA%40mail.gmail.com.
