LGTM1 On Tue, Feb 11, 2025 at 10:06 AM Nan Lin <lin...@chromium.org> wrote:
> Hi Blink Owners, > > Just friendly ping, are there any more questions for this feature please? > > We hope to get the approvals before Feb 18 so that we can still target > M134 for the feature. > > Thanks, > Nan > > On Wed, Feb 5, 2025 at 11:42 AM Nan Lin <lin...@chromium.org> wrote: > >> Hi Yoav, >> >> Thanks for the response. >> >> On Wed, Feb 5, 2025 at 11:14 AM Yoav Weiss (@Shopify) < >> yoavwe...@chromium.org> wrote: >> >>> >>> >>> On Tuesday, January 28, 2025 at 8:19:10 PM UTC+1 Akash Nadan wrote: >>> >>> Hi Mike, >>> >>> Thanks for flagging this. We have requested all of the bits in the >>> chromestatus entry. >>> >>> Thanks, >>> Akash >>> >>> On Tuesday, January 28, 2025 at 7:17:03 AM UTC-8 Mike Taylor wrote: >>> >>> Please request the various bits in your chromestatus entry, thanks. >>> On 1/24/25 5:05 PM, 'Akash Nadan' via blink-dev wrote: >>> >>> Contact emails >>> >>> akash...@google.com, lin...@chromium.org, john...@chromium.org, >>> arp...@chromium.org >>> >>> >>> Explainer >>> >>> 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> >>> >>> TAG review >>> >>> Original I2S for the Attribution Reporting API - Closed >>> <https://github.com/w3ctag/design-reviews/issues/724> >>> >>> TAG review status >>> >>> Declined >>> <https://github.com/w3ctag/design-reviews/issues/724#issuecomment-2234828340> >>> >>> Summary >>> >>> We are landing the following change to the Attribution Reporting API >>> focused on: >>> >>> - >>> >>> Removing aggregatable report limit when trigger context ID is >>> non-null >>> >>> >>> This change is based on API caller feedback and the need for being able >>> to measure a higher number of conversion events for certain user flows. >>> >>> Currently the API has a limit that allows up to 20 aggregatable reports >>> to be generated per source registration which is restrictive for use cases >>> where a user may have a longer user journey. This change removes the >>> aggregatable report limit when a trigger context ID is provided as part of >>> the registration. >>> >>> >>> Can you expand a bit on what this limit is protecting against, and why >>> it's fine to remove it when there's a non-null context ID? What are the >>> tradeoffs here? >>> >> >> Since the presence or absence of an attribution report leaks some >> potentially sensitive cross-site data, the browser will add noise to hide >> the true number of reports by randomly sending noisy null reports for some >> fraction of trigger registrations (see explainer >> <https://github.com/WICG/attribution-reporting-api/blob/main/AGGREGATE.md#hide-the-true-number-of-attribution-reports> >> ). >> The limit on the number of aggregatable reports per source is to limit >> the abuse of the protection. >> >> When the trigger context ID is specified, the browser will >> unconditionally send an aggregatable report, either a real report or a null >> report, therefore it fully protects the true number of reports and the >> limit is unncecessary. >> >>> >>> >>> The removal of this limit is restricted to only when the trigger context >>> ID is specified, because when it is specified the API applies a higher rate >>> of null reports which helps to protect against cross-site information >>> leaking through report counts. >>> >>> Additionally, aggregatable reports will still be bound by other limits >>> that restrict the total amount of information that can be measured, such as >>> the L1 contribution budget (65,536) per source and the attribution rate >>> limit. >>> >>> Explainer/Spec changes >>> >>> 1. >>> >>> Explainer & Spec: https://github.com/WICG/attribution-reporting-api/ >>> pull/1475 >>> >>> >>> Risks >>> Interoperability and Compatibility >>> >>> This change is not a fully backwards compatible change. There’s no API >>> surface change, but it can cause the API to behave differently given the >>> same set of inputs. The API caller may receive more aggregatable reports if >>> they use the trigger context ID feature, whereas previously if they tried >>> to generate more than 20 aggregatable reports for a given source >>> registration, then any reports beyond 20 would be rejected and not >>> generated. This change is unlikely to cause any issues for API callers >>> given they will still be able to receive the reports they currently receive >>> without any changes. Additionally, this feature does not break any >>> pre-existing API or web functionality. >>> >>> Gecko: No signal (Original request: https://github.com/mozilla/ >>> standards-positions/issues/791) >>> >>> WebKit: No signal (Original request: https://github.com/WebKit/ >>> standards-positions/issues/180) >>> >>> >>> 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? >>> >>> No >>> >>> >>> Will this feature be supported on all six Blink platforms (Windows, Mac, >>> Linux, Chrome OS, Android, and Android WebView)? >>> >>> This feature is expected to be supported in Android WebView in the >>> future alongside Android platform support. >>> <https://developers.google.com/privacy-sandbox/private-advertising/attribution-reporting/android> >>> >>> Is this feature fully tested by web-platform-tests >>> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> >>> ? >>> >>> No, currently this feature is not covered in WPT 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 feature is anticipated to ship as part of Chrome M134 >>> <https://chromiumdash.appspot.com/schedule>. >>> >>> Link to entry on the Chrome Platform Status >>> >>> https://chromestatus.com/feature/5079048977645568 >>> >>> 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> >>> >>> Intent to Ship: Attribution Reporting features M123 >>> <https://groups.google.com/a/chromium.org/g/blink-dev/c/NE7VGke1Bjc/m/bIX00t4CAAAJ> >>> >>> Intent to Ship: Attribution Reporting features M124 >>> <https://groups.google.com/a/chromium.org/g/blink-dev/c/aregp1li6xk/m/IhBB2z8tBQAJ> >>> >>> Intent to Ship: Attribution Reporting features M125 >>> <https://groups.google.com/a/chromium.org/g/blink-dev/c/9UyhI6SRyxM/m/zgWWckgWAQAJ> >>> >>> Intent to Ship: Attribution Reporting features M126 >>> <https://groups.google.com/a/chromium.org/g/blink-dev/c/7UQR2lPn5KE/m/q_kL6ZiJDgAJ> >>> >>> Intent to Ship: Attribution Reporting features M127 >>> <https://groups.google.com/a/chromium.org/g/blink-dev/c/LAgnyPsJyJg?pli=1> >>> >>> Intent to Ship: Attribution Reporting features M128 (1) >>> <https://groups.google.com/a/chromium.org/g/blink-dev/c/qlsv7fn0zRE/m/SK8upePCCAAJ> >>> >>> Intent to Ship: Attribution Reporting features M128 (2) >>> <https://groups.google.com/a/chromium.org/g/blink-dev/c/VKGn41wMYlg/m/VsNXktqvCAAJ> >>> >>> Intent to Ship: Attribution Reporting features M130 >>> <https://groups.google.com/a/chromium.org/g/blink-dev/c/-K2xDYuvmmA/m/Fhp564I7AgAJ> >>> >>> Intent to Ship: Attribution Reporting features M132 (1) >>> <https://groups.google.com/a/chromium.org/g/blink-dev/c/T6i4a_hNeXk/m/Z1WwZTZMAAAJ> >>> >>> Intent to Ship: Attribution Reporting features M132 (2) >>> <https://groups.google.com/a/chromium.org/g/blink-dev/c/pc6n8o-S_Ns/m/sWah9fSmAQAJ> >>> >>> -- >>> 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+...@chromium.org. >>> >>> >>> To view this discussion visit https://groups.google.com/a/ >>> chromium.org/d/msgid/blink-dev/9910bd89-51a5-4766-b3b7- >>> afd0412ff602n%40chromium.org >>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/9910bd89-51a5-4766-b3b7-afd0412ff602n%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 visit >>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/ba5863c0-4b49-4204-8940-be08d3f90f8fn%40chromium.org >>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/ba5863c0-4b49-4204-8940-be08d3f90f8fn%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 visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CA%2BVrgPkP9cM5izDEU-T7jtC%3D-VYdK6cPW00uP62DnD%3Dk-w67iA%40mail.gmail.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CA%2BVrgPkP9cM5izDEU-T7jtC%3D-VYdK6cPW00uP62DnD%3Dk-w67iA%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 blink-dev+unsubscr...@chromium.org. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw9bGJuzj98G-aBtznT8rLym45K4iQCecr6_dDuskPm_ew%40mail.gmail.com.
