← back to v150 · deprecate-and-remove-related-website-sets-rws
conformance · v150
v150 · deprecate-and-remove-related-website-sets-rws — conformance probe
5 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
5
total
| id | contract | kind | verdict | detail |
|---|---|---|---|---|
storage-access-still-present |
document.requestStorageAccess remains available — RWS removal does not affect the Storage Access API itself. | typeof | … | |
well-known-related-website-set-no-longer-honored |
Fetching /.well-known/related-website-set.json from another origin does not produce side-effects in browser policy (this is hard to feature-detect; we probe by checking the page can construct a request to that URL without error). | script | … | |
rws-membership-not-exposed-via-cookie-store |
cookieStore (if present) does not expose a related-website-set membership accessor (no such IDL existed; this guards against an accidental re-add). | script | … | |
permission-storage-access-still-queryable |
navigator.permissions.query({name:'storage-access'}) still resolves; the user-grant path is preserved post-RWS removal. | script | … | |
cookie-samesite-still-enforced |
Setting a SameSite=Lax cookie via document.cookie is still possible — SameSite enforcement (which RWS partly relaxed) remains live. | script | … |