Closed Bug 1908208 Opened 1 year ago Closed 1 year ago

[wpt-sync] Sync PR 47161 - [wpt] upgrade saa tests to non-tentative

Categories

(Core :: Privacy: Anti-Tracking, task, P4)

task

Tracking

()

RESOLVED FIXED
130 Branch
Tracking Status
firefox130 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Ari Chivukula <arichiv@chromium.org> wrote:

[wpt] upgrade saa tests to non-tentative

These are supported cross vendor:
https://privacycg.github.io/requestStorageAccessFor/
https://privacycg.github.io/storage-access/

Bug: 353425617
Change-Id: I9b9cace143baa4a6740cf2fad032e6ff9c814cea
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5714249
Commit-Queue: Steven Bingler \<bingler@chromium.org>
Auto-Submit: Ari Chivukula \<arichiv@chromium.org>
Reviewed-by: Steven Bingler \<bingler@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1328261}

Component: web-platform-tests → Privacy: Anti-Tracking
Product: Testing → Core

CI Results

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

Total 8 tests and 2 subtests

Status Summary

Firefox

OK : 8
PASS : 15
FAIL : 23

Chrome

OK : 8
PASS : 31
FAIL : 7

Safari

OK : 5
PASS : 3
FAIL : 29
TIMEOUT: 6
NOTRUN : 3

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

  • /top-level-storage-access-api/requestStorageAccessFor-insecure.sub.window.html [wpt.fyi]
    • [top-level-context] document.requestStorageAccessFor() should be supported on the document interface: FAIL (Chrome: PASS, Safari: FAIL)
    • [top-level-context] document.requestStorageAccessFor() should be rejected by default with no user gesture: FAIL (Chrome: PASS, Safari: FAIL)
    • [non-fully-active] document.requestStorageAccessFor() should not resolve when run in a detached frame: FAIL (Chrome: PASS, Safari: FAIL)
    • [non-fully-active] document.requestStorageAccessFor() should not resolve when run in a detached DOMParser document: FAIL (Chrome: PASS, Safari: FAIL)
    • [frame-on-insecure-page] document.requestStorageAccessFor() should be supported on the document interface in embedded iframes: FAIL (Chrome: PASS, Safari: FAIL)
    • [frame-on-insecure-page] document.requestStorageAccessFor() should be rejected when called in an iframe: FAIL (Chrome: PASS, Safari: FAIL)
    • [top-level-context] document.requestStorageAccessFor() should be rejected when called in an insecure context: FAIL (Chrome: PASS, Safari: FAIL)
  • /top-level-storage-access-api/requestStorageAccessFor.sub.https.window.html [wpt.fyi]
    • [top-level-context] document.requestStorageAccessFor() should be supported on the document interface: FAIL (Chrome: PASS, Safari: FAIL)
    • [top-level-context] document.requestStorageAccessFor() should be rejected when called with no argument: FAIL (Chrome: PASS, Safari: FAIL)
    • [top-level-context] document.requestStorageAccessFor() should be rejected by default with no user gesture: FAIL (Chrome: PASS, Safari: FAIL)
    • [non-fully-active] document.requestStorageAccessFor() should not resolve when run in a detached frame: FAIL (Chrome: PASS, Safari: FAIL)
    • [non-fully-active] document.requestStorageAccessFor() should not resolve when run in a detached DOMParser document: FAIL (Chrome: PASS, Safari: FAIL)
    • [top-level-context] document.requestStorageAccessFor() should be resolved without a user gesture with an existing permission: FAIL (Chrome: PASS, Safari: FAIL)
    • [top-level-context] document.requestStorageAccess() should be resolved without a user gesture after a successful requestStorageAccessFor() call: FAIL (Chrome: FAIL, Safari: FAIL)
    • [top-level-context] document.requestStorageAccessFor() should be resolved when called properly with a user gesture and the same origin: FAIL (Chrome: PASS, Safari: FAIL)
    • [top-level-context] document.requestStorageAccessFor() should be rejected when called with an invalid origin: FAIL (Chrome: PASS, Safari: FAIL)
    • [top-level-context] document.requestStorageAccessFor() should be rejected when called with an opaque origin: FAIL (Chrome: PASS, Safari: FAIL)
    • [top-level-context] Top-level storage access only allows cross-site subresource requests to access cookie when using CORS mode.: FAIL (Chrome: FAIL, Safari: FAIL)
    • [same-origin-iframe] document.requestStorageAccessFor() should be supported on the document interface: FAIL (Chrome: PASS, Safari: FAIL)
    • [same-origin-iframe] document.requestStorageAccessFor() should be rejected when called with no argument: FAIL (Chrome: PASS, Safari: FAIL)
    • [same-origin-iframe] document.requestStorageAccessFor() should be rejected when called in an iframe: FAIL (Chrome: PASS, Safari: FAIL)
    • [same-origin-iframe] Existing top-level storage access permission should not allow cookie access for the cross-site subresource requests made in a non-top-level context.: FAIL (Chrome: PASS, Safari: FAIL)
  • /top-level-storage-access-api/top-level-storage-access-permission.sub.https.window.html [wpt.fyi]
    • Permission default state can be queried: FAIL (Chrome: PASS, Safari: FAIL)
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/b998b4720494 [wpt PR 47161] - [wpt] upgrade saa tests to non-tentative, a=testonly https://hg.mozilla.org/integration/autoland/rev/bd4b8f542330 [wpt PR 47161] - Update wpt metadata, a=testonly
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 130 Branch
You need to log in before you can comment on or make changes to this bug.