LGTM3 On Tuesday, December 5, 2023 at 8:43:13 PM UTC+1 Mike Taylor wrote:
> LGTM2 > On 12/5/23 2:29 PM, Rick Byers wrote: > > LGTM1 > > On the interoperability risks front I see there's still no official > position on the API from Mozilla > <https://github.com/mozilla/standards-positions/issues/791> or WebKit > <https://github.com/WebKit/standards-positions/issues/180>. > > On Thu, Nov 30, 2023 at 3:38 PM 'Akash Nadan' via blink-dev < > [email protected]> wrote: > >> Contact emails >> >> [email protected], [email protected], [email protected] >> >> 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: >> >> - >> >> reducing transmission loss by supporting reduced aggregatable report >> delays with trigger context ID >> - >> >> additional API configurability by supporting an event-level reporting >> epsilon field >> - >> >> improve extensibility of the API by failing registrations when >> encountering reserved keys >> >> Explainer/Spec changes >> >> - Reduce aggregate delays and support trigger context ID >> <https://github.com/WICG/attribution-reporting-api/pull/1114> >> - >> >> Event-level reporting epsilon field >> <https://github.com/WICG/attribution-reporting-api/pull/1097> >> - >> >> Reserve keys starting with an underscore >> <https://github.com/WICG/attribution-reporting-api/pull/967> >> >> >> Risks >> Interoperability and Compatibility >> >> The first two changes (1. supporting reduced aggregatable report delays >> and 2. supporting event-level reporting epsilon field) are fully backwards >> compatible changes. Both of these features are optional features. >> >> The third change (3. failing registrations when encountering reserved >> keys) is backwards incompatible. Any keys starting with an underscore will >> cause the registration to fail. We have checked the usage of such keys, and >> the data shows that keys that start with an underscore are not currently >> used. Therefore this change will most likely not break any current >> registrations or have minimal impact. >> >> >> 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 121 >> >> Link to entry on the Chrome Platform Status >> >> https://chromestatus.com/feature/5181611197071360 >> >> 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> >> >> -- >> 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/e20140d1-74ea-4535-b20a-9bfd89e27954n%40chromium.org >> >> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/e20140d1-74ea-4535-b20a-9bfd89e27954n%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 [email protected]. > > To view this discussion on the web visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFUtAY9PJTQ%2Bv3saBbBs3rzJT%3DrZPR35EQfVU%2BgYt-HUtTgzaQ%40mail.gmail.com > > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFUtAY9PJTQ%2Bv3saBbBs3rzJT%3DrZPR35EQfVU%2BgYt-HUtTgzaQ%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/9c3e3b20-653e-4ced-904c-24d715ce9af9n%40chromium.org.
