Closed Bug 1870646 Opened 1 year ago Closed 1 year ago

[wpt-sync] Sync PR 43710 - Fenced frames: window.fence.disableUntrustedNetwork API surface

Categories

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

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

Tracking

(firefox123 fixed)

Status:
RESOLVED FIXED
Milestone:
123 Branch
Tracking Flags:
Tracking Status
firefox123 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

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

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

Garrett Tanzer <gtanzer@chromium.org> wrote:

Fenced frames: window.fence.disableUntrustedNetwork API surface

Add nonfunctional window.fence.disableUntrustedNetwork API surface
(behind feature flag), which is not available in urn iframes. Later CLs
will gradually make it functional.

This entails the following internal changes:

  • New field can_disable_untrusted_network_ in FencedFrameConfig.
    Currently true for fenced frames, but disabled for urn iframes at the
    same time as partition nonce.
  • New fields can_disable_untrusted_network_ and
    has_disabled_untrusted_network_ in FencedFrameProperties.
    can_disable_untrusted_network_ is sent to same-origin renderers to
    gate availability of the window.fence.disableUntrustedNetwork API.
  • Navigations through the FencedFrameConfig(url) constructor now store
    url as the mapped url in the resulting FencedFrameProperties, so
    that we can perform same- vs. cross-origin checks for availability of
    window.fence.disableUntrustedNetwork.

I2P: https://groups.google.com/a/chromium.org/g/blink-dev/c/ofii__csdOY

Bug: 1294933
Change-Id: I13ec7a570bd7d84b2bc3780b577e318b4d103e9a

Reviewed-on: https://chromium-review.googlesource.com/5124560
WPT-Export-Revision: 2fa4f9dfba7f4266e1239c64879b1c3a38a8893d

CI Results

Ran 0 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

GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/df5fd102d633 [wpt PR 43710] - Fenced frames: window.fence.disableUntrustedNetwork API surface, a=testonly https://hg.mozilla.org/integration/autoland/rev/7d891c3313b0 [wpt PR 43710] - Update wpt metadata, a=testonly

https://hg.mozilla.org/mozilla-central/rev/df5fd102d633
https://hg.mozilla.org/mozilla-central/rev/7d891c3313b0

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