v135 · service workers

SW Scope Audit

Configure a service worker scope and a series of pushState navigation routes. The audit shows what Client.url the SW sees (creation URL — unchanged by pushState in Chrome 135) and which routes would previously have caused scope-mismatch bugs where the SW appeared to not intercept certain pages.

checking Service Worker API…

Chrome 135 makes Client.url reflect the document's creation URL (the URL it was navigated to), not the latest history.pushState() destination. Before Chrome 135, a SPA doing pushState to /app/dashboard would show that URL in Client.url, confusing SW scope matching and clients.matchAll() filters.

Configuration

Document creation URL (SW client URL)

Service worker scope

pushState routes (the SPA navigates to these)

Scope match analysis

pushState URL	Pre-135: Client.url used for scope	Chrome 135: Client.url = creation URL	Changed?
Click "Run scope audit" to analyse.

What clients.matchAll() sees (Chrome 135)

Run the audit to see the result.