LGTM1. This looks like a small, well-considered change that makes the platform more consistent. I agree the compat risks are small.
>From what I understand, fields like TAG review and standards-positions for other browsers should be covered by the larger umbrella feature, so we shouldn't block on them. However, I would encourage you to include those fields in future Intents, stating that rationale for omitting the reviews. On Sat, May 18, 2024 at 1:21 AM 'Akash Nadan' via blink-dev < blink-dev@chromium.org> wrote: > Contact emails > > akashna...@google.com, lin...@chromium.org, johni...@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 are landing the following change to the Attribution Reporting API > focused on: > > - > > applying element-level referrer policy for specific html elements > > > This change is based on ad-tech feedback > <https://github.com/WICG/attribution-reporting-api/issues/382> and so > that attributionsrc requests are treated like other subresources on the > page. > > Currently when the API is called through the use of the attributionsrc > attribution as part of various html elements (i.e. <img>, <script>, <a>, or > window.open), it ignores the resource-level referrer policy attribute set > on the html element. > > With this change the attributionsrc request will now apply the same > resource-level referrer policy set in the <img>, <script>, <a>, or > window.open. > > This will allow ad-techs more control over whether or not they want to be > more or less restrictive regarding the referrer information on their > attributionsrc requests. > > Explainer/Spec changes > > 1. > > Use referrer policy for background attributionsrc requests > <https://github.com/WICG/attribution-reporting-api/pull/1254> > > > Risks > Interoperability and Compatibility > > This feature is not a strictly backwards compatible change because before > the change the resource-level policy was ignored, but now it is not > ignored. Given this change, the value of the request's referrer header may > be different than before. This breakage is unlikely, because it would > require an API caller to have a different referrer policy on the document > and on the resource, which is unlikely for the Attribution Reporting API. > > > Will this feature be supported on all six Blink platforms (Windows, Mac, > Linux, Chrome OS, Android, and Android WebView)? > > The attribution reporting feature will be supported on all platforms with > the exception of 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 > > This feature is anticipated to ship as part of Chrome 126 > <https://chromiumdash.appspot.com/schedule>. > > Link to entry on the Chrome Platform Status > > https://chromestatus.com/feature/5191009960198144 > > 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> > > Intern to Ship: Attribution Reporting features M125 > <https://groups.google.com/a/chromium.org/g/blink-dev/c/9UyhI6SRyxM/m/zgWWckgWAQAJ> > > -- > 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/8c39d27a-ae43-40ce-bd32-4656b82fe867n%40chromium.org > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/8c39d27a-ae43-40ce-bd32-4656b82fe867n%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/CAM0wra_ZDxT1FVpnCvKnTXw4CE_EiDXjUhqmOHXbfwZ02QxaCg%40mail.gmail.com.
