Chrome 152 removed support for Attribution Reporting API
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
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
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from mdn/browser-compat-data
-
Web extensions - Safari Technology Preview 257 data and the message_serialization manifest keyPossibly taken @xeenon claimed this today. Openneeds triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
mdn/browser-compat-data#31192 ·
Maintainers usually reply within 1 day
-
api.WGSLLanguageFeatures - Firefox supports three featuresPossibly taken @Manishram-ai claimed this 1 day ago. Opendata:api needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
mdn/browser-compat-data#31175 ·
Maintainers usually reply within 1 day
-
needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
mdn/browser-compat-data#31069 · 1 comment ·
Maintainers usually reply within 1 day
-
needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
mdn/browser-compat-data#31057 · 2 comments ·
Maintainers usually reply within 1 day
-
api.Window.devicePixelRatio - Does change with page zoom in Safari (webkit)Possibly taken @Manishram-ai claimed this 1 day ago. Opendata:api needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
mdn/browser-compat-data#31039 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
All issues in mdn/browser-compat-data
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
firefly-iii/firefly-iii#13259 · 3 comments ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
molgenis/molgenis-emx2#7059 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
[DOCS/SMU] Correct the 1 GiB window bullet and the coverage-target sentence in the SMU datasheetOpenDOCS SMU
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
tenstorrent/tt-oca-harness#3931 ·
Maintainers usually reply within 1 day
-
[Sync EN] Document the getLastErrors() return value change in the PHP 8.2 migration guide (#6107)Opensync-en
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Maintainers usually reply within 1 day