Re: [whatwg/fetch] Script-created redirects responses have no location URL (#1146)

Ohhhh, yes I did misunderstand it! I think I assumed step 3 was an early return and forgot about it. I agree with you now there's no spec change needed to get to Safari's behavior. What I thought was a spec bug works just fine.

WDYT about an editorial change to switch location URL from state to a computed property anyway? It's a little weird that (unless I'm still confused), when a SW is juggling response objects, they sometimes have the internal location URL attached, and sometimes don't (depending on if it was script- or network-constructed). It doesn't matter because the SW forwards the response object up to HTTP fetch, we'll compute or recompute the location URL anyway. But the spec models it as state, so it's not obvious it doesn't actually need to be, say, persisted in CacheStorage.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/1146#issuecomment-769624814