← back to v134 · support-web-locks-api-in-shared-storage
conformance · v134
v134 · support-web-locks-api-in-shared-storage — conformance probe
6 assertions drawn from the spec. Each is a single contract the spec text makes. Pass/fail reflects what this browser executed; blocked means the contract was not run because it needs user mediation, hardware, or another unavailable precondition. Open the page in Chrome stable / canary / Firefox / Safari to compare.
0
pass
0
fail
0
blocked
6
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
shared-storage-exists |
window.sharedStorage exists — the storage scope the lock guards. | exists | … | |
web-locks-api-exists |
navigator.locks (Web Locks API) is exposed and is the lock manager Shared Storage integrates with. | exists | … | |
web-locks-request-fn |
navigator.locks.request is callable from the page side. | typeof | … | |
shared-storage-batchupdate |
sharedStorage.batchUpdate is exposed (the recommended atomic-mutation surface that benefits from locks). | script | … | |
shared-storage-set |
sharedStorage.set is callable — writes guarded by Web Locks when the worklet uses navigator.locks. | typeof | … | |
web-locks-query-fn |
navigator.locks.query lets the page inspect currently held locks. | typeof | … |