You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm wary of adding this support. It'd require xhr2 to choose a DOM parser for people, and I don't think there's a universally accepted parser. Also, doing this would require a good amount of research, because I'd want a parser that meets the WHATWG / W3C specs.
If you don't need portable code, I'd suggest using whatever parser you'd like on responseText. If you do, perhaps try a DOMParser polyfill?
For example, https://github.com/jindw/xmldom looks good, but it only supports DOM2. If that's sufficient for your purposes, it might do the trick.
Why not use xmldom then? That's what I use and it's working great AFAIK and DOM2 is better than nothing. No need to make this a hard requirement, you could make it optional and ask for a DOM parser implementation and expect the W3C format?
As for web workers, I don't get why would I use this library with web workers, aren't people using web worker using the native browser XMLHttpRequest?
I don't see any support for that attribute, however it seems that it is in the spec:
http://www.w3.org/TR/XMLHttpRequest/#the-responsexml-attribute
I think it would be really easy to integrate a DOMParser kind of object and add this extension.
What do you think?
Edit: I would contribute a pull request upon confirmation that this an issue, but I'd also require some hint as to how to integrate the xml parser.
The text was updated successfully, but these errors were encountered: