← back to v139 · web-app-scope-extensions
conformance · v139
v139 · web-app-scope-extensions — 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 |
|---|---|---|---|---|
navigator-service-worker-exposed |
navigator.serviceWorker is exposed; web apps that use scope_extensions still rely on SW registration scope. | exists | … | |
service-worker-register-method |
ServiceWorkerContainer.prototype.register is exposed; this method's options dictionary still includes scope. | typeof | … | |
fetch-still-works-for-manifest |
fetch() is exposed; the browser parses the web app manifest (with scope_extensions) using fetch under the hood. | typeof | … | |
window-launch-queue-exposed |
window.launchQueue is exposed in Chrome installed-PWA contexts; cross-origin launches that scope_extensions enables flow through it. | script | … | |
link-manifest-rel |
<link rel=manifest> remains the way to declare a manifest; scope_extensions is a new field inside that manifest JSON. | script | … | |
navigation-api-still-exposed |
window.navigation is exposed in Chrome; cross-origin navigations within scope_extensions still surface through the Navigation API where applicable. spec ↗ | script | … |