Re: [w3c/ServiceWorker] Inconsistencies in ServiceWorkerClients get and matchAll implementations (Issue #1734)

Digging on `matchAll`, it seems that setting ` includeUncontrolled: true` will align Chrome's results with shipping safari.

Digging on `get`, it seems from testing that Chrome will wait for the service worker to provide a response object, but will not wait to start parsing the response body.

Only Firefox is exposing `about:blank` URLs.
If calling `matchAll` or `get`, the client URL will, at some point migrate from `about:blank` to the fetch event request URL.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/issues/1734#issuecomment-2454603146
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/ServiceWorker/issues/1734/2454603146@github.com>

Received on Monday, 4 November 2024 12:35:39 UTC