Re: [whatwg/fetch] Browsers preserve fragments on redirects (#505)

What was the reason for not exposing fragments in the past?

Exposing them makes sense without considering compatibility issues, but changing the API has some risks - For example, if a hash table keyed with Response.url, may be broken with the change.

-- 
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/505#issuecomment-366664487