Closed Bug 1831914 Opened 2 years ago Closed 1 year ago

[wpt-sync] Sync PR 39889 - Fenced frame: permissions refactor to match spec

Categories

(Testing :: web-platform-tests, task, P4)

Product:
Testing
Component:
web-platform-tests
Type:
task

Tracking

(firefox116 fixed)

Status:
RESOLVED FIXED
Milestone:
116 Branch
Tracking Flags:
Tracking Status
firefox116 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

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

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

Liam Brady <lbrady@google.com> wrote:

Fenced frame: permissions refactor to match spec

Change-Id: I00acb013076d527e482b3ce8f4bd0e45a93c5cf8
Reviewed-on: https://chromium-review.googlesource.com/4514455
WPT-Export-Revision: 67ac7993542d015ca6b3158cd84428955c5d871e

PR 39889 applied with additional changes from upstream: f42fbed1f92ac02906a18ea014d162e7aa3bedd8
Try push failed: decision task bcCaaYP5QWWNZMuMeIwVLg returned error

CI Results

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

Total 3 tests and 3 subtests

Status Summary

Firefox

OK : 3
FAIL: 8

Chrome

OK : 3
FAIL: 8

Safari

OK : 3
FAIL: 8

Links

GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

  • /fenced-frame/config-cross-origin-apis.https.html [wpt.fyi]
    • A fenced frame that navigates itself to a cross origin page loses window.fence API access.: FAIL (Chrome: FAIL, Safari: FAIL)
    • A cross-origin iframe inside a fenced frame does not get window.fence API access.: FAIL (Chrome: FAIL, Safari: FAIL)
  • /fenced-frame/default-enabled-features-allow-all.https.html [wpt.fyi]
    • Same-origin fenced frame loads when feature policies are *: FAIL (Chrome: FAIL, Safari: FAIL)
    • Cross-origin fenced frame loads when feature policies are *: FAIL (Chrome: FAIL, Safari: FAIL)
    • A fenced frame that navigates itself to a cross origin page that allows feature policies can still access the feature policies: FAIL (Chrome: FAIL, Safari: FAIL)
  • /fenced-frame/default-enabled-features-allow-self.https.html [wpt.fyi]
    • Same-origin fenced frame does not when feature policies are self: FAIL (Chrome: FAIL, Safari: FAIL)
    • Cross-origin fenced frame does not load when feature policies are self: FAIL (Chrome: FAIL, Safari: FAIL)
    • Fenced frames default feature policies are set to not allow anything.: FAIL (Chrome: FAIL, Safari: FAIL)
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/37aea98405af [wpt PR 39889] - Fenced frame: permissions refactor to match spec., a=testonly https://hg.mozilla.org/integration/autoland/rev/fbb9da9b026a [wpt PR 39889] - Update wpt metadata, a=testonly

https://hg.mozilla.org/mozilla-central/rev/37aea98405af
https://hg.mozilla.org/mozilla-central/rev/fbb9da9b026a

Status: NEW → RESOLVED
Closed: 1 year ago
status-firefox116: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 116 Branch
You need to log in before you can comment on or make changes to this bug.