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

Of course it would be best for the WPT tests to reflect the current spec. I would rather they fail in a nicer way than just timeout, e.g. instead just fail one assertion like that fetch-event.https.html test.

In the particular case of clients-get-worker, I'd probably vote to remove the clientId check and just rely on fetch-event.https.html for test coverage.

I'm still wondering though if we needed to make the change from null to empty string for client ids.. what did resultingClientId and targetClientId have to do with that decision?

-- 
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-361607198