Closed Bug 1829930 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 39695 - Fenced frames: Flesh out storage partitioning WPTs

Categories

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

task

Tracking

(firefox115 fixed)

RESOLVED FIXED
115 Branch
Tracking Status
firefox115 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Garrett Tanzer <gtanzer@chromium.org> wrote:

Fenced frames: Flesh out storage partitioning WPTs

Bug: 1123606
Change-Id: Ica07abf663063c4679f4728fd362e3d50c06c0d3
Reviewed-on: https://chromium-review.googlesource.com/4475985
WPT-Export-Revision: 61e108a8115a9ed4ab0ca7793fdf6e0e8bb7ffe7

Try push failed: decision task UtL90YNUQkeqUMIssKifcA returned error

CI Results

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

Total 1 tests and 6 subtests

Status Summary

Firefox

OK : 1
FAIL: 6

Chrome

OK : 1
FAIL: 6

Safari

OK : 1
FAIL: 6

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

  • /fenced-frame/storage-partitioning.https.html [wpt.fyi]
    • document.cookie: FAIL (Chrome: FAIL, Safari: FAIL)
    • localStorage: FAIL (Chrome: FAIL, Safari: FAIL)
    • sessionStorage: FAIL (Chrome: FAIL, Safari: FAIL)
    • Cache API: FAIL (Chrome: FAIL, Safari: FAIL)
    • File System Access API: FAIL (Chrome: FAIL, Safari: FAIL)
    • IndexedDB: FAIL (Chrome: FAIL, Safari: FAIL)
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/22baca723940 [wpt PR 39695] - Fenced frames: Flesh out storage partitioning WPTs, a=testonly https://hg.mozilla.org/integration/autoland/rev/6bc23970c910 [wpt PR 39695] - Update wpt metadata, a=testonly
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 115 Branch
You need to log in before you can comment on or make changes to this bug.