- From: Ben Kelly <notifications@github.com>
- Date: Wed, 17 Feb 2021 13:45:02 -0800
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 17 February 2021 21:45:15 UTC
@wanderview commented on this pull request. > @@ -3835,6 +3836,13 @@ these steps: </ul> <p>then return a <a>network error</a>. + + <li> + <p>Set <var>actualResponse</var>'s <a for=response>URL</a>'s <a for=url>fragment</a> to + <var>request</var>'s <a for=request>current URL</a>'s <a for=url>fragment</a>. + + <p class=note>There is currently no mechanism for the service worker to control + <var>actualResponse</var>'s <a for=response>URL</a>'s <a for=url>fragment</a>. I agree It would be nice if respondWith() functioned similar to redirects when it came to fragments. -- 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/pull/696#discussion_r577966130
Received on Wednesday, 17 February 2021 21:45:15 UTC