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 >> >> [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: >> >> - >> >> 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 [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/d92f72cb-1298-4ec2-8355-72bd7c9e5766n%40chromium.org.
