[whatwg/fetch] Consider changing Response's url so it includes a fragment (#1167)

I initially bundled this with #505 and I now think that was a mistake. We should consider this separately. We also don't need to change `XMLHttpRequest`'s `responseURL` as that's a legacy API. An obvious alternative here would be to introduce a separate getter for the propagated fragment if we deem it too risky.

Not exposing this prevents correct usage of fragments in userland. (I'm not sure there is much of that as we haven't seen any complaints to date, but it seems consistent with the extensible web principles to give userland the same capabilities the browser has.)

I will adjust https://github.com/web-platform-tests/wpt/pull/7261 per our decision.

cc @wanderview @yutakahirano @KershawChang @youennf @domenic @jasnell

-- 
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/1167