-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Element.attributes should be a NamedNodeMap #853
Comments
The toString problem: yes, definitely fixable; pull request welcome. The own-properties problem: kind of. We could fix your particular example by making the underscored-properties non-enumerable, which is not very hard. But if we wanted to protect against |
Awesome.. will take a deeper look. |
Regardless of the example, why not making it a NamedNodeMap? |
Oh hey, fixed this in 5.4.0. |
I wasn't able to get NamedNodeMap, even using Object.prototype.toString.call(domElement.attributes) neither using domElement.attributes.toString(), both returns [object Object] Im using the following code:
I will create a new issue since this is issue is too old |
Chrome: "[object NamedNodeMap]"
jsdom: "[object Object]"
Also...
Chrome: []
jsdom: [ '_ownerDocument', '_parentNode', '_readonly' ]
This is breaking a script that copies attributes from one element onto another.
Is this something that's fixable?
The text was updated successfully, but these errors were encountered: