[w3c/ServiceWorker] FetchEvent: Add origin check before setting replacesClientId (Issue #1679)

As part of implementing [`replacesClientId`](https://w3c.github.io/ServiceWorker/#ref-for-dom-fetchevent-replacesclientid%E2%91%A1), the issue of what to do in the event of a cross-origin navigation came up. In such a case, `replacesClientId` will be the id of a client whose origin is different from the service worker handling the fetch event. 

So, it feels as if [Step 24.3.9 of Handle Fetch](https://w3c.github.io/ServiceWorker/#handle-fetch) should include a same origin check and initialize `replacesClientId` to the empty string if it fails?

I can also write additional tests for this specific situation as part of https://github.com/WebKit/WebKit/pull/13130

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

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