storage-access-api

edit

WPT coverage of the tests of storage-access-api at the revision c8fa86fb13d4. The tests link to their results in the browsers on wpt.fyi. The tentative tests (experimental features), the reftests and the crash tests are listed separately from the stable tests.

GroupPassingTestsDisabledPass rate
Stable3437092%
Tentative15020%
Reftests000–
Crash tests000–
All3542083%

Failure reasons

The tests that do not pass (failing or disabled), by kind of reason. A test with several reasons counts once per kind.

  • TEST BUG: 4
  • NOT IMPLEMENTED: 4

Stable tests

TestResultSubtestsKindDescription
hasStorageAccess-ABA.sub.https.window.jsPass3 / 3
hasStorageAccess-insecure.sub.window.jsPass15 / 15
hasStorageAccess.sub.https.window.jsPass15 / 15
idlharness.window.jsPass12 / 12
requestStorageAccess-ABA.sub.https.window.jsPass4 / 4
requestStorageAccess-cross-origin-fetch.sub.https.window.jsPass2 / 2
requestStorageAccess-cross-origin-iframe-navigation-relax.sub.https.window.jsFail1 / 2TEST BUG1 subtest: expects a document to keep its storage access when its same-site parent navigates it to its own origin (Chromium); the specification only keeps the storage access of a navigation initiated by the active document of the navigable (the environment id of the source snapshot params, https://privacycg.github.io/storage-access/#navigation)
requestStorageAccess-cross-origin-iframe-navigation.sub.https.window.jsPass4 / 4
requestStorageAccess-cross-site-fetch.sub.https.window.jsPass1 / 1
requestStorageAccess-cross-site-iframe.sub.https.window.jsPass4 / 4
requestStorageAccess-cross-site-sibling-iframes.sub.https.window.jsPass2 / 2
requestStorageAccess-dedicated-worker.sub.https.window.jsPass2 / 2
requestStorageAccess-insecure.sub.window.jsPass13 / 13
requestStorageAccess-nested-cross-origin-iframe.sub.https.window.jsPass4 / 4
requestStorageAccess-nested-cross-site-iframe.sub.https.window.jsPass4 / 4
requestStorageAccess-nested-same-origin-iframe.sub.https.window.jsPass4 / 4
requestStorageAccess-non-fully-active.sub.https.window.jsPass2 / 2
requestStorageAccess-same-site-iframe.sub.https.window.jsPass4 / 4
requestStorageAccess-sandboxed-iframe-allow-storage-access.sub.https.window.jsPass1 / 1
requestStorageAccess-sandboxed-iframe-no-storage-access.sub.https.window.jsPass3 / 3
requestStorageAccess-web-socket.sub.https.window.jsFail1 / 2TEST BUG1 subtest: expects the WebSocket handshake to wss://{{hosts[alt][]}}:{{ports[wss][0]}} to send the unpartitioned cookie of the frame that has storage access, but the port of the WebSocket server is not the port of the frame: the request is not same origin with the frame, so it is not eligible for storage access (https://privacycg.github.io/storage-access/#determine-the-initial-storage-access-eligibility)
requestStorageAccess.sub.https.window.jsPass4 / 4
storage-access-beyond-cookies.BroadcastChannel.sub.https.window.jsPass1 / 1
storage-access-beyond-cookies.SharedWorker.sub.https.window.jsFail0 / 1NOT IMPLEMENTEDthe sameSiteCookies option of SharedWorker (https://privacycg.github.io/saa-non-cookie-storage/#shared-workers, an incubation that the HTML Standard does not have): the option is ignored, so StorageAccessHandle.SharedWorker() does not throw for sameSiteCookies: 'all' in a third-party context, the shared workers are not keyed by it, and the requests of a worker created with none send the SameSite cookies; the shared workers are also keyed by the top-level site only, so the partitioned worker of the frame (same site with the top-level document, embedded by a cross-site frame) is the relay worker of the top-level document
storage-access-beyond-cookies.blobStorage.sub.https.window.jsPass1 / 1
storage-access-beyond-cookies.caches.sub.https.window.jsPass1 / 1
storage-access-beyond-cookies.cookies.sub.https.window.jsPass1 / 1
storage-access-beyond-cookies.estimate.sub.https.window.jsPass1 / 1
storage-access-beyond-cookies.getDirectory.sub.https.window.jsPass1 / 1
storage-access-beyond-cookies.indexedDB.sub.https.window.jsPass1 / 1
storage-access-beyond-cookies.localStorage.sub.https.window.jsPass1 / 1
storage-access-beyond-cookies.locks.sub.https.window.jsPass1 / 1
storage-access-beyond-cookies.none.sub.https.window.jsPass1 / 1
storage-access-beyond-cookies.sessionStorage.sub.https.window.jsPass1 / 1
storage-access-beyond-cookies.thirdPartyBlobStorage.sub.https.window.jsPass1 / 1
storage-access-permission.sub.https.window.jsPass7 / 7
storageAccess.testdriver.sub.htmlPass1 / 1

Tentative tests

TestResultSubtestsKindDescription
requestStorageAccess-service-worker.sub.https.tentative.window.jsFail2 / 3TEST BUG1 subtest: the control expects the WebSocket handshake of the frame to wss://{{hosts[alt][]}}:{{ports[wss][0]}} to send the unpartitioned cookie, but the port of the WebSocket server is not the port of the frame: the request is not same origin with the frame, so it is not eligible for storage access (https://privacycg.github.io/storage-access/#determine-the-initial-storage-access-eligibility)
requestStorageAccess-shared-worker.sub.https.tentative.window.jsFail0 / 3TEST BUG, NOT IMPLEMENTED1 subtest: the control expects the WebSocket handshake of the frame to wss://{{hosts[alt][]}}:{{ports[wss][0]}} to send the unpartitioned cookie, but the port of the WebSocket server is not the port of the frame: the request is not same origin with the frame, so it is not eligible for storage access (https://privacycg.github.io/storage-access/#determine-the-initial-storage-access-eligibility); 2 subtests: the third-party context of a shared worker: the requests of a shared worker created by a cross-site frame are first-party for the cookies, so the cookie jar does not block its unpartitioned cookies
storage-access-beyond-cookies.BlobURLDedicatedWorker.sub.https.tentative.window.jsFail0 / 1NOT IMPLEMENTEDthe storage access of the dedicated workers: the blob URLs are partitioned by storage key, and a dedicated worker created by the third-party frame after its storage access was granted does not get it, so it cannot fetch the blob URL that StorageAccessHandle.createObjectURL() created in the first-party partition
storage-access-beyond-cookies.BlobURLSharedWorker.sub.https.tentative.window.jsTimeout0 / 1NOT IMPLEMENTEDthe blob URLs of StorageAccessHandle.createObjectURL() as the script of a shared worker: the third-party frame cannot fetch the blob URL of the first-party partition, so new SharedWorker() fires an error event, and the test then waits for the message of a shared worker created by the handle, which is not relayed (the test times out)
storage-access-headers.tentative.https.sub.window.jsPass4 / 4