Closed Bug 1649442 Opened 4 years ago Closed 4 years ago

[wpt-sync] Sync PR 24395 - [CSP] Add WPT tests for inheritance with window.open.

Categories

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

Product:
Core
Component:
DOM: Security
Type:
task

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla80
Tracking Flags:
Tracking Status
firefox80 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

(
URL
)

Details

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

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

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

arthursonzogni <arthursonzogni@chromium.org> wrote:

[CSP] Add WPT tests for inheritance with window.open.

There are WPT tests about CSP inheritance when opening local-scheme.
This is tested for iframe. Testing for iframes is good, testing for
both iframes and opened window is better.

Initially, I wanted to reproduce bug 1073126, but failed to do so. I
still want to keep the tests.

Bug:chromium:1073126
Change-Id: I4c363037d556bf93f37d43dd5b84a1da608d5e44
Reviewed-on: https://chromium-review.googlesource.com/2274602
WPT-Export-Revision: e4817afa0772edc4c40dc9403ac1b628eed36050

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

CI Results

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

Total 1 tests and 10 subtests

Status Summary

Firefox

OK : 1
PASS: 10

Chrome

OK : 1
PASS: 10

Safari

OK : 1
PASS: 10

Links

GitHub PR Head
GitHub PR Base

Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/467c18ce5ae2
[wpt PR 24395] - [CSP] Add WPT tests for inheritance with window.open., a=testonly

https://hg.mozilla.org/mozilla-central/rev/467c18ce5ae2

Status: NEW → RESOLVED
Closed: 4 years ago
status-firefox80: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla80
You need to log in before you can comment on or make changes to this bug.