Contact emails akashna...@google.com, lin...@chromium.org, johni...@chromium.org
Blink component Internals > AttributionReporting <https://bugs.chromium.org/p/chromium/issues/list?q=component:Internals%3EAttributionReporting> Summary Currently the aggregation key identifier length limit ( https://wicg.github.io/attribution-reporting-api/#max-length-per-aggregation-key-identifier) is checked in both source and trigger registrations. As this limit is not for privacy and it's not persisted in the storage, we are removing this limit in trigger registrations. This is consistent with other fields in the trigger registrations, e.g. filters and scopes, whose size is only checked in source registrations, but not trigger registrations. Explainer/Spec changes 1. Spec: https://github.com/WICG/attribution-reporting-api/pull/1435 Risks This change introduces slightly different behavior when long aggregation key identifiers (i.e. aggregation keys that exceed the limit <https://wicg.github.io/attribution-reporting-api/#max-length-per-aggregation-key-identifier>) are specified in the trigger registration. Prior to M131, trigger registrations that specify long aggregation key identifiers would be dropped. Starting from M131, those trigger registrations would still be processed for attribution, but the aggregatable trigger data or aggregatable values specified with the long aggregation key identifier would be ignored effectively and not included in the final attribution reports (i.e. if a report is generated for the trigger registration). Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)? All except for Android WebView Is this feature fully tested by web-platform-tests <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> ? No, due to difficulty of adding significant coverage for Attribution Reporting API because of API-mandated delays and noise. However, the feature is covered by comprehensive integration tests (commonly referred to as “interop tests”) that are also reusable by other implementations. Estimated milestones This change is anticipated to ship as part of Chrome 131 <https://chromiumdash.appspot.com/schedule>. Link to entry on the Chrome Platform Status https://chromestatus.com/feature/5131578140000256 -- 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/4fe803c8-b09c-4a2f-ab28-e4fffb75e0fdn%40chromium.org.
