mdn / mdn/browser-compat-data

`html.elements.a.attributionDestination` - Missing keys for private click measurement

Open
#25,595 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

browser:safari data:html
Dominant language
JSON
Stars
5.8k
Forks
2.6k
Avg merge
1d 21h
Merged PRs (30d)
186

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?

Private click measurement data is incomplete; two keys I'd expect to exist are missing.

What browsers does this problem apply to, if applicable?

No response

What did you expect to see?

I'd expect to see keys for:

  • html.elements.a.attributiondestination
  • api.HTMLAnchorElement.attributionDestination

with support shown in Safari.

Did you test this? If so, how?

I didn't test it properly (it's a rather complex API), but "attributionDestination" in HTMLAnchorElement.prototype returns true in the current version of Safari. That said, I'd expect the data to be equivalent to the already-recorded attributionsourceid attribute.

Can you link to any release notes, bugs, pull requests, or MDN pages related to this?
Do you have anything more you want to share?

Discovered while reviewing https://github.com/web-platform-dx/web-features/pull/2467.

MDN URL

No response

MDN metadata

No response

Contributor guide

Open the contributing guide

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.

Research direction

Start with the html.elements.a.attributiondestination and api.HTMLAnchorElement.attributionDestination entries named in the issue, comparing them with the existing attributionsourceid data. Check the linked Private Click Measurement specification and WebKit release notes, then confirm both keys report Safari support consistently.

Written by the indexing model from the issue text.

Assessment

Tech stack
html, javascript
Domain
web-dev
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.