-
Notifications
You must be signed in to change notification settings - Fork 170
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
Note that the Permission Policy has default * for the Chromium OT #551
Conversation
Co-authored-by: Andrew Paseltiner <apaseltiner@google.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we also update https://wicg.github.io/attribution-reporting-api/#permission-policy-integration in this PR?
Sure, added the change. |
This CL also adds logic for sending a warning issue to devtools if the API was used in a context where it might break in the future when this change is reverted. See WICG/attribution-reporting-api#551 Bug: 1360563 Change-Id: I9a04b3ce9dbab5ab432c963419cb173e232aa881 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3877268 Reviewed-by: Ian Clelland <iclelland@chromium.org> Reviewed-by: John Delaney <johnidel@chromium.org> Reviewed-by: Andrey Kosyakov <caseq@chromium.org> Commit-Queue: Charlie Harrison <csharrison@chromium.org> Reviewed-by: Nate Chapin <japhet@chromium.org> Reviewed-by: Andrew Paseltiner <apaseltiner@chromium.org> Cr-Commit-Position: refs/heads/main@{#1045172}
This CL also adds logic for sending a warning issue to devtools if the API was used in a context where it might break in the future when this change is reverted. See WICG/attribution-reporting-api#551 (cherry picked from commit e959519) Bug: 1360563 Change-Id: I9a04b3ce9dbab5ab432c963419cb173e232aa881 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3877268 Reviewed-by: Ian Clelland <iclelland@chromium.org> Reviewed-by: John Delaney <johnidel@chromium.org> Reviewed-by: Andrey Kosyakov <caseq@chromium.org> Commit-Queue: Charlie Harrison <csharrison@chromium.org> Reviewed-by: Nate Chapin <japhet@chromium.org> Reviewed-by: Andrew Paseltiner <apaseltiner@chromium.org> Cr-Original-Commit-Position: refs/heads/main@{#1045172} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3900731 Commit-Queue: Andrew Paseltiner <apaseltiner@chromium.org> Cr-Commit-Position: refs/branch-heads/5249@{#465} Cr-Branched-From: 4f7bea5-refs/heads/main@{#1036826}
This CL also adds logic for sending a warning issue to devtools if the API was used in a context where it might break in the future when this change is reverted. See WICG/attribution-reporting-api#551 Bug: 1360563 Change-Id: I9a04b3ce9dbab5ab432c963419cb173e232aa881 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3877268 Reviewed-by: Ian Clelland <iclelland@chromium.org> Reviewed-by: John Delaney <johnidel@chromium.org> Reviewed-by: Andrey Kosyakov <caseq@chromium.org> Commit-Queue: Charlie Harrison <csharrison@chromium.org> Reviewed-by: Nate Chapin <japhet@chromium.org> Reviewed-by: Andrew Paseltiner <apaseltiner@chromium.org> Cr-Commit-Position: refs/heads/main@{#1045172} NOKEYCHECK=True GitOrigin-RevId: e959519cfe885d8387f53a50ba8271465dc06347
(Note this PR was meant to address #519, for posterity) |
Preview | Diff