storage-access-api
editWPT 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.
| Group | Passing | Tests | Disabled | Pass rate |
|---|---|---|---|---|
| Stable | 34 | 37 | 0 | 92% |
| Tentative | 1 | 5 | 0 | 20% |
| Reftests | 0 | 0 | 0 | – |
| Crash tests | 0 | 0 | 0 | – |
| All | 35 | 42 | 0 | 83% |
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
Tentative tests
| Test | Result | Subtests | Kind | Description |
|---|---|---|---|---|
requestStorageAccess-service-worker.sub.https.tentative.window.js | Fail | 2 / 3 | TEST BUG | 1 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.js | Fail | 0 / 3 | TEST BUG, NOT IMPLEMENTED | 1 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.js | Fail | 0 / 1 | NOT IMPLEMENTED | the 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.js | Timeout | 0 / 1 | NOT IMPLEMENTED | the 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.js | Pass | 4 / 4 |