Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set node.localName #8

Open
moll opened this issue Feb 17, 2015 · 3 comments
Open

Set node.localName #8

moll opened this issue Feb 17, 2015 · 3 comments
Assignees

Comments

@moll
Copy link

moll commented Feb 17, 2015

Hey,

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. :-)

@Stuk
Copy link
Contributor

Stuk commented Feb 19, 2015

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.

@moll
Copy link
Author

moll commented Feb 20, 2015

Cool! Thanks.

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. :-)

@moll
Copy link
Author

moll commented Feb 20, 2015

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.

PS. Totally hijacking a thread, I know. 😇

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants