This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
We should be clear about what responseXML's Document's object associated URL needs to be. See: http://lists.w3.org/Archives/Public/public-webapps/2010OctDec/0241.html
This is clear now. But maybe we should also expose something like responseURL in case there is no document, but you want to resolve relative URLs in say, JSON?
Document's URL was defined in http://dvcs.w3.org/hg/xhr/rev/ca4c13d638f9
> maybe we should also expose something like responseURL in case > there is no document, but you want to resolve relative URLs in say, JSON? -1 - it does not feel "natural" to me to resolve URLs that are not in a "document" according to the resource's URL. (On the other hand, I've often wanted something like an xhr.requestURL property for debugging..sometimes while stepping through code one might come across an XHR object reference and need to know what URL it was used for. There are workarounds, but they are clunky.)
You mean like in a cache manifest? Of course it's natural.
Hm.. I guess you're right, also matches resolution of relative URLs in CSS. A responseURL property seems like a good idea.
*** Bug 23361 has been marked as a duplicate of this bug. ***
I think it should also at least include the redirect status code plus the final request method (because of the "occasional" rewriting to GET).
That doesn't seem like sufficient reason, but it's also out of scope of this bug. https://github.com/whatwg/xhr/commit/0c9670185b79c255211881e086e05e7a99e65f06