Preserve fragment in Request/Response URLs

[ParkFramework]

Removing #hash of URL, it prevents to use history API:

fetch("url#hash").then(response => history.pushState(null, null, response.url))

The server redirect, response.url needed use, that correct display url in address bar.
I do propose to not delete the #hash, it will be more convenient in practice.

Request.url and Response.url should be similarly URL.href (within #hash)

[wanderview]

Are hashes maintained through server side redirects for xhr? Or another existing API?

[annevk]

Yeah, they are. I guess we should probably revert this "fetch URL" thing. 😟

[ParkFramework]

All is well, the only problem auto deletion #hash from Request.url

new Request('/url#hash') // request.url === 'http://example.org/url' (without #hash)

[wanderview]

If we make this change I worry about places in service worker spec where we might be relying on the hash being removed from the url.

[annevk]

@jungkees @jakearchibald any thoughts on the above comment from @wanderview?

[wanderview]

I know we had a previous issue about removing the spec from service worker script. Maybe all that stuff is explicit, but I know we've depended on fetch spec to have certain side effects before for other things. I guess its just something to double-check.

[wanderview]

I guess this would expose the hashes to the fetch event where previously they were not exposed.

It also creates a new requirement on Cache API to store hashes. The Cache match algorithm would also have to be updated to take into account hashes.

[annevk]

Note that I argued in w3c/ServiceWorker#854 (comment) that responses never have a fragment identifier. What happens with redirects is that the fragment from the Location header URL can end up being important. Not a fragment on a response, which isn't really a thing.

[wanderview]

Gecko bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1264178

[mfalken]

Chrome status: https://www.chromestatus.com/feature/4753419730419712
Chrome bug: https://bugs.chromium.org/p/chromium/issues/detail?id=624278