[Guides] Delete guides for Attribution Reporting API

[bershanskiy]

Description

Delete guides for Attribution Reporting API

Motivation

Google deprecated Attribution Reporting API and since Google Chrome 150 invocations for field-trial enabled browsers will always reject.

Additional details

Source: Intent to Deprecate and Remove: Attribution Reporting API

Related issues and pull requests

[github-actions]

Preview URLs (13 pages)

• /en-US/docs/Web/API/Attribution_Reporting_API
• /en-US/docs/Web/API/HTMLAnchorElement/attributionSrc
• /en-US/docs/Web/API/HTMLImageElement
• /en-US/docs/Web/API/HTMLScriptElement/attributionSrc
• /en-US/docs/Web/API/HTMLScriptElement
• /en-US/docs/Web/API/RequestInit
• /en-US/docs/Web/API/XMLHttpRequest/setAttributionReporting
• /en-US/docs/Web/HTML/Reference/Elements/a
• /en-US/docs/Web/HTML/Reference/Elements/img
• /en-US/docs/Web/HTML/Reference/Elements/script
• /en-US/docs/Web/HTTP/Reference/Headers/Attribution-Reporting-Eligible
• /en-US/docs/Web/HTTP/Reference/Headers/Attribution-Reporting-Register-Source
• /en-US/docs/Web/HTTP/Reference/Headers/Attribution-Reporting-Register-Trigger

[bershanskiy]

As a reminder, Safari and Firefox opposed Attribution Reporting API and never supported it. Attribution Reporting API in Google Chrome requires website enrollment and Google suspended enrollment after deprecating Google Privacy Sandbox project. In effect, Attribution Reporting API is accessible only to websites with active enrollment in old Google Chrome browsers (version 149 and below) or embedded browsers without support for field trial configs (e.g., WebView).

[pepelsbey]

Hey! Let's take a pause here, removing content. It requires prior discussion, not just PR-review-done.

/cc @hamishwillee

[bershanskiy]

Sure, there is no rush to remove these guides.

[hamishwillee]

Hey! Let's take a pause here, removing content. It requires prior discussion, not just PR-review-done.

@pepelsbey FWIW I've previously approved these removal PRs because it isn't just a matter that these are deprecated - the features are removed from current browsers and you can't use them in old browsers unless you're already signed up to the (closed for new business) enrollment process. In other words, there is no one that can benefit from these docs.

I'm happy with that removal decision. I'd be even happier if BCD agreed to remove the reference and we started with that.

[pepelsbey]

I'm happy with that removal decision. I'd be even happier if BCD agreed to remove the reference and we started with that.

I think it's something we need to discuss first. It's more complicated than that: there were resources spent by our partners putting it on MDN, for example, etc.

I'd even discuss with the vendor first, if it aligns with the removal process. Some developers might still rely on these docs.

[bershanskiy]

If MDN maintainers prefer, I can prepare a PR restoring all Privacy Sandbox content.

I was not aware of any continued interest in this content, given the API deprecations and lack of maintenance (e.g., prose suggesting that the API access registrations are still available).

[hamishwillee]

Thanks @pepelsbey. Please let @bershanskiy know if you want this restored or if it can wait following the results of your discussions.

[hamishwillee]

Removing myself as reviewer and adding @pepelsbey

[bershanskiy]

Who should we reach out to? [blink-dev] Intent to Deprecate and Remove: Attribution Reporting API provides a public mail thread regarding this deprecation. If you would like to communicate privately, the first message provides three contact emails.

Alternatively, we can just wait two or more Chromium milestones until Google Chrome 152 ships complete removal of Attribution Reporting APIs implementations and removes them with stubs.