respondWith uses the wrong targetRealm

[isonmad]

Since 6c2b3f1 both FetchEvent.respondWith and ForeignFetchEvent.respondWith say

   1. Let |targetRealm| be the <a>relevant Realm</a> of the <a>context object</a>.

But the relevant Realm of the context object is always going to be the service worker itself, isn't it?

It looks like targetRealm should be 'event.request's request's client's Realm.'

[jakearchibald]

But the relevant Realm of the context object is always going to be the service worker itself, isn't it?

Looking at the spec, I think that's the intention. @jungkees?

[mkruisselbrink]

I'm not sure... looking at the PR that added this text it seems the goal was to somehow transfer the stream to a different realm, which isn't what the current text does. @yutakahirano or @domenic probably know best what was intended?

[isonmad]

Looking at the spec, I think that's the intention.

How do you figure that? It makes no sense to copy from a ReadableStream that already exists in the service worker to a second, newly constructed ReadableStream... that is also created in the service worker.

Isn't the whole point of respondWith supposed to send a Response from the SW to the client, not to itself?

[domenic]

This indeed looks like a bug. The idea is to send it to the client's realm. The fix @isonmad suggests in the OP seems correct to me (I guess "this FetchEvent's request's request's client's Realm" is the most correct way of getting at things.)