Re: [w3c/ServiceWorker] Until resultingClientId is implemented, what should FetchEvent.clientId be for navigation requests? (#1266)

Thanks for flagging this. I just noticed the fetch-event.https.html test also changed and Chrome and Firefox are failing in the same way for "Service Worker responds to fetch event with an existing client id" at https://wpt.fyi/service-workers/service-worker/fetch-event.https.html.

Is there a reason we decided empty string is better than null to indicate "no id"?

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