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
That's from DOM 2, but having localName available (even if as an alias to tagName) would make Minidom compatible with the Xpath library out of the box. I think. :-)
The text was updated successfully, but these errors were encountered:
It is actually from level 1, and I've just looked at bringing across the latest changes from JSDom which include this property. Sadly it wasn't straight forward, so: yep this will happen when I get a bit of time.
While you're at it, would you mind taking a look at why the Xpath library breaks on Minidom Node's attributes? It seems to work with the XMLDOM library, though. :-)
Or do you happen to know of a decoupled querySelector implementation that one could use with the returned DOM from Minidom if Xpath's not a go? All of the ones I've found so far have been tied to a global documents object.
Hey,
That's from DOM 2, but having
localName
available (even if as an alias totagName
) would make Minidom compatible with the Xpath library out of the box. I think. :-)The text was updated successfully, but these errors were encountered: