You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As part of implementing replacesClientId, 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 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 WebKit/WebKit#13130
The text was updated successfully, but these errors were encountered:
gterzian
changed the title
FetchEvent: Add origin check before setting replacesClientId
FetchEvent: add origin check before setting replacesClientId
May 17, 2023
As part of implementing
replacesClientId
, 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 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 WebKit/WebKit#13130
The text was updated successfully, but these errors were encountered: