Add support for Reporting-Endpoints (#37965)

Does not yet handle failures of endpoints, which requires us to update
metadata. I don't see that metadata being used anywhere, so I am not
sure if there is WPT coverage for it.

Part of #37238

Signed-off-by: Tim van der Lippe <tvanderlippe@gmail.com>
This commit is contained in:
Tim van der Lippe 2025-07-09 21:07:29 +02:00 committed by GitHub
parent 16aca5516d
commit 70c57c6136
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
13 changed files with 439 additions and 22 deletions

View file

@ -1,6 +1,3 @@
[report-to-directive-allowed-in-meta.https.sub.html]
[Report is observable to ReportingObserver]
expected: FAIL
[Violation report status OK.]
expected: FAIL

View file

@ -1,6 +1,3 @@
[reporting-api-sends-reports-on-violation.https.sub.html]
[Report is observable to ReportingObserver]
expected: FAIL
[Violation report status OK.]
expected: FAIL

View file

@ -1,3 +0,0 @@
[cross-origin-report-no-credentials.https.sub.html]
[Reporting endpoints did not receive credentials.]
expected: FAIL

View file

@ -1,3 +0,0 @@
[cross-origin-same-site-credentials.https.sub.html]
[Reporting endpoints received credentials.]
expected: FAIL

View file

@ -1,3 +0,0 @@
[same-origin-report-credentials.https.sub.html]
[Reporting endpoints received credentials.]
expected: FAIL

View file

@ -1,3 +0,0 @@
[same-origin-same-site-credentials.https.sub.html]
[Reporting endpoints received credentials.]
expected: FAIL