[wpt-sync] Sync PR 34801 - Add WPTs for COOP: restrict-properties 4/*
Categories
(Core :: DOM: Core & HTML, task, P4)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox104 | --- | fixed |
People
(Reporter: mozilla.org, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 34801 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/34801
Details from upstream follow.
Arthur Hemery <ahemery@chromium.org> wrote:
Add WPTs for COOP: restrict-properties 4/*
Verify that a restrict-properties boundary cannot be crossed by named
targeting, and that it is impossible to get the location object across
that boundary.Bug: 1330586
Change-Id: I5a30b762c65acbac2b8907564e5ece58a9a4e54eReviewed-on: https://chromium-review.googlesource.com/3755549
WPT-Export-Revision: 406cb9ee5b6cd93667a4c47cccc35961cd7629a3
|
Assignee | |
Updated•2 years ago
|
|
|
Assignee | |
Comment 1•2 years ago
|
||
|
|
Assignee | |
Comment 2•2 years ago
|
||
CI Results
Ran 9 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
FAIL: 1
Chrome
OK : 1
FAIL: 1
Safari
OK : 1
FAIL: 1
Links
Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base
Details
New Tests That Don't Pass
- /html/cross-origin-opener-policy/tentative/restrict-properties/named_targeting.https.html [wpt.fyi]
- Verify that named targeting does not work across isolation boundaries.:
FAIL(Chrome:FAIL, Safari:FAIL)
- Verify that named targeting does not work across isolation boundaries.:
|
||
Comment 4•2 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/10da7feab960
https://hg.mozilla.org/mozilla-central/rev/92a56e83cbad
Description
•