Chrome 152 removed support for Attribution Reporting API

Open
#31,008 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
28/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
json
Domain
documentation

Research direction

This is a tracking issue, so there is no single file to edit. Start from the linked Chromium removal bug (issues.chromium.org/513231893) to see which Attribution Reporting API features were removed in Chrome 152 and which were stubbed until Chrome 159. Each affected Attribution Reporting entry in the browser-compat-data JSON then needs its support data updated, and the maintainer will track those per-API changes here. Done means each affected entry reflects the removal.

Written by the indexing model from the issue text.

Description

needs triage
What type of issue is this?

Incorrect support data (example: BrowserX says "86" but support was added in "40")

What information was incorrect, unhelpful, or incomplete?

All BCD entries related to Attribution Reporting API need to be updated to note changes. Some features were removed outright since Chrome 152 while others were stubbed-out and remained until Chrome 159.

This is a tracking issue which I will reference to track individual updates to APIs.

What browsers does this problem apply to, if applicable?

Chromium (Chrome, Edge 79+, Opera, Samsung Browser)

What did you expect to see?

Updated tables.

Did you test this? If so, how?

This issue tracks removal (multiple commits): https://issues.chromium.org/issues/513231893

Can you link to any release notes, bugs, pull requests, or MDN pages related to this?

No response

Do you have anything more you want to share?

No response

MDN URL

No response

MDN metadata

No response

Dominant language
JSON
Stars
5.8k
Forks
2.7k
Avg merge
2d 20h
Merged PRs (30d)
160

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mdn/browser-compat-data

All issues in mdn/browser-compat-data

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.