Closed Bug 1657089 Opened 4 years ago Closed 4 years ago

[wpt-sync] Sync PR 24871 - Add WPT for CSP frame-ancestors violation reporting with report-uri

Categories

(Core :: DOM: Security, task, P4)

task

Tracking

()

RESOLVED FIXED
81 Branch
Tracking Status
firefox81 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream][domsecurity-backlog])

Sync web-platform-tests PR 24871 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/24871
Details from upstream follow.

Antonio Sartori <antoniosartori@chromium.org> wrote:

Add WPT for CSP frame-ancestors violation reporting with report-uri

This CL implements a simple WPT that tests if Content-Security-Policy
violation reporting works for a frame-ancestors violation when the
reporting endpoint is specified with the report-uri directive.

Bug: 1096845
Change-Id: I65e6b8618cdcf68bfe8a88228d1d500e98740295
Reviewed-on: https://chromium-review.googlesource.com/2336594
WPT-Export-Revision: 26b6db4093a17bf60146f3c04058ebc5ca0f2981

Component: web-platform-tests → DOM: Security
Product: Testing → Core
Whiteboard: [wptsync downstream] → [wptsync downstream][domsecurity-backlog]

CI Results

Ran 12 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 1 tests and 1 subtests

Status Summary

Firefox

OK : 1
PASS: 1

Chrome

OK : 1
PASS: 1

Safari

OK : 1
PASS: 1

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/e8c9be6a1132 [wpt PR 24871] - Add WPT for CSP frame-ancestors violation reporting with report-uri, a=testonly
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/960805e49b59 [wpt PR 24871] - Add WPT for CSP frame-ancestors violation reporting with report-uri, a=testonly
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → 81 Branch
You need to log in before you can comment on or make changes to this bug.