Closed Bug 1836522 Opened 1 years ago Closed 1 year ago

[wpt-sync] Sync PR 40367 - Allow SharedStorage APIs in FLEDGE fenced frames.

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: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

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

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

Liam Brady <lbrady@google.com> wrote:

Allow SharedStorage APIs in FLEDGE fenced frames.

Right now, features like SharedStorage's selectURL() are not allowed
inside of a fenced frame created with FLEDGE. There is no
security/privacy benefit to having this restriction, so it should be
removed to have consistent behavior across fenced frames loaded with
different APIs.

Bug: 1450902
Change-Id: I5714e584ee445eab2d2c42c654cb0fd1971ce691

Reviewed-on: https://chromium-review.googlesource.com/4584988
WPT-Export-Revision: 3e959ff958f0e86a4798a4de8223ebbbb997c503

CI Results

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

Total 9 tests and 4 subtests

Status Summary

Firefox

OK : 9
FAIL: 23

Chrome

OK : 9
FAIL: 23

Safari

OK : 9
FAIL: 23

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

  • /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-none.https.html [wpt.fyi]
    • Same-origin fenced frame does not load when feature policies are none: FAIL (Chrome: FAIL, Safari: FAIL)
    • Cross-origin fenced frame does not load when feature policies are none: FAIL (Chrome: FAIL, Safari: FAIL)
  • /fenced-frame/default-enabled-features-allow-self.https.html [wpt.fyi]
    • Same-origin fenced frame loads when feature policies are self: 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)
    • A fenced frame redirected to a page that does not allow feature policies does not navigate: FAIL
    • Same-origin fenced frame does not when feature policies are self: FAIL (Chrome: FAIL, Safari: FAIL)
  • /fenced-frame/default-enabled-features-attribute-allow.https.html [wpt.fyi]
    • Same-origin fenced frame with allow attribute enabling required features: FAIL (Chrome: FAIL, Safari: FAIL)
    • Cross-origin fenced frame with allow attribute enabling required features: FAIL (Chrome: FAIL, Safari: FAIL)
    • Delivered policies can further restrict permissions of a fenced frame: FAIL (Chrome: FAIL, Safari: FAIL)
  • /fenced-frame/default-enabled-features-attribute-change.https.html [wpt.fyi]
    • Changing the allow attribute is a no-op for the current navigation: FAIL (Chrome: FAIL, Safari: FAIL)
    • Changing the allow attribute is a no-op for frame-initiated navigations: FAIL (Chrome: FAIL, Safari: FAIL)
  • /fenced-frame/default-enabled-features-attribute-disallow.https.html [wpt.fyi]
    • Same-origin fenced frame with allow attribute disabling required feature: FAIL (Chrome: FAIL, Safari: FAIL)
    • Cross-origin fenced frame with allow attribute disabling required feature: FAIL (Chrome: FAIL, Safari: FAIL)
  • /fenced-frame/default-enabled-features-attribution-disabled.https.html [wpt.fyi]
    • Same-origin fenced frame with allow attribute enabling required feature but page disabling feature.: FAIL (Chrome: FAIL, Safari: FAIL)
    • Cross-origin fenced frame with allow attribute enabling required feature but page disabling feature.: FAIL (Chrome: FAIL, Safari: FAIL)
  • /fenced-frame/default-enabled-features-unset.https.html [wpt.fyi]
    • Same-origin fenced frame loads when feature policies are unset: FAIL (Chrome: FAIL, Safari: FAIL)
    • Cross-origin fenced frame loads when feature policies are unset: FAIL (Chrome: FAIL, Safari: FAIL)
  • /fenced-frame/resolve-to-config-promise.https.html [wpt.fyi]
    • resolveToConfig set to a promise that resolves to true: FAIL (Chrome: FAIL, Safari: FAIL)
    • resolveToConfig set to a promise that resolves to false: FAIL (Chrome: FAIL, Safari: FAIL)
    • resolveToConfig set to a promise that immediately resolves: FAIL (Chrome: FAIL, Safari: FAIL)
    • resolveToConfig set to a promise that resolves to an invalid value: FAIL (Chrome: FAIL, Safari: FAIL)
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/a75abec51be8 [wpt PR 40367] - Allow SharedStorage APIs in FLEDGE fenced frames., a=testonly

https://hg.mozilla.org/mozilla-central/rev/a75abec51be8

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.