Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replace dedicated JS registration APIs with generic mechanism via fetch #428

Merged
merged 5 commits into from
May 16, 2022
Merged

Replace dedicated JS registration APIs with generic mechanism via fetch #428

merged 5 commits into from
May 16, 2022

Conversation

apasel422
Copy link
Collaborator

#378
Closes #363

@apasel422 apasel422 marked this pull request as ready for review May 16, 2022 13:50
EVENT.md Show resolved Hide resolved
Copy link
Collaborator

@csharrison csharrison left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@johnivdel
Copy link
Collaborator

Could we add a blurb stating the browser should process responses for any request that has these headers? It would be good to make clear xhr/etc work as well. Otherwise lgtm

@apasel422 apasel422 merged commit b13a83d into WICG:main May 16, 2022
@apasel422 apasel422 deleted the js-fetch branch May 16, 2022 16:28
aarongable pushed a commit to chromium/chromium that referenced this pull request May 19, 2022
It is being replaced with a more general fetch mechanism:

WICG/attribution-reporting-api#428

Bug: 1325874
Change-Id: Iaed47963d99f20fc8bbd0d04cf6e92714980c9f5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3649346
Commit-Queue: Andrew Paseltiner <apaseltiner@chromium.org>
Reviewed-by: Nate Chapin <japhet@chromium.org>
Reviewed-by: John Delaney <johnidel@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1005332}
mjfroman pushed a commit to mjfroman/moz-libwebrtc-third-party that referenced this pull request Oct 14, 2022
It is being replaced with a more general fetch mechanism:

WICG/attribution-reporting-api#428

Bug: 1325874
Change-Id: Iaed47963d99f20fc8bbd0d04cf6e92714980c9f5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3649346
Commit-Queue: Andrew Paseltiner <apaseltiner@chromium.org>
Reviewed-by: Nate Chapin <japhet@chromium.org>
Reviewed-by: John Delaney <johnidel@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1005332}
NOKEYCHECK=True
GitOrigin-RevId: d77d9d7b7251fc0c5fdcf6d4f603dfa8a3020058
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Is window.attributionReporting.registerTrigger necessary?
3 participants