Closed Bug 1518392 Opened 5 years ago Closed 5 years ago

[wpt-sync] Sync PR 14744 - content-security-policy/unsafe-hashes/javascript_src_allowed-href-blank.html assumes the javascript url will run in the wrong browsing context

Categories

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

enhancement

Tracking

()

RESOLVED FIXED
mozilla67
Tracking Status
firefox67 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

()

Details

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

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

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

Nate Chapin <japhet@chromium.org> wrote:

content-security-policy/unsafe-hashes/javascript_src_allowed-href-blank.html assumes the javascript url will run in the wrong browsing context

Bug: 638435
Change-Id: I75ae1a26bbbdbd993bfffde38909f3e83013a6cf
Reviewed-on: https://chromium-review.googlesource.com/1399546
WPT-Export-Revision: 4d390acf00854bd5ba4096065e601b48b1709531

Component: web-platform-tests → DOM: Security
Product: Testing → Core
Whiteboard: [wptsync downstream] → [wptsync downstream][domsecurity-backlog]
Whiteboard: [wptsync downstream][domsecurity-backlog] → [wptsync downstream]
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Ran 1 tests and 1 subtests
OK     : 1
FAIL   : 1
Whiteboard: [wptsync downstream] → [wptsync downstream][domsecurity-backlog]
Pushed by james@hoppipolla.co.uk:
https://hg.mozilla.org/integration/mozilla-inbound/rev/6d067109d8f2
[wpt PR 14744] - content-security-policy/unsafe-hashes/javascript_src_allowed-href-blank.html assumes the javascript url will run in the wrong browsing context, a=testonly
Pushed by james@hoppipolla.co.uk:
https://hg.mozilla.org/integration/mozilla-inbound/rev/bd4d72879bd4
[wpt PR 14744] - content-security-policy/unsafe-hashes/javascript_src_allowed-href-blank.html assumes the javascript url will run in the wrong browsing context, a=testonly
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla67
You need to log in before you can comment on or make changes to this bug.