Elment.attributes does not implement the NamedNodeMap interface

[sondr]

I was trying to replace JSDOM with Happy DOM and the app was failing to run something akin to:

const element = document.createElement('div');
const someAttribute = document.createAttribute('someattribute');
element.attributes.setNamedItem(someAttribute);

I see the current implementation is:

readonly attributes: { [k: string]: Attr | number };

Is there any chance there will be a switch to NamedNodeMap in the future?

[capricorn86]

Hi @sondr! 🙂

Yes I will add support for this as soon as possible. This will probably come in pretty soon as it is fairly easy to implement support for.

[urkle]

This is needed to support vue-test-utils (1.x) as it uses attributes.length and attributes.item(#)

[brattonross]

I ran into an issue related to this when running tests with axe-core. It looks like in their code there are a couple of if statements that do a check along the lines of:

if (attributes instanceof window.NamedNodeMap) {
 // ...
}

This results in the error Right-hand side of 'instanceof' is not an object being thrown, and the tests failing.

I think this is a little different to the original issue since this is concerning window and not an element, although I could be wrong

[Archon-]

Code such as this in Jest tests:

expect(wrapper.find('.button').attributes().disabled).toEqual('disabled')

Throw an error: TypeError: attributes.item is not a function. Seems like it's the same issue. Is this in active development? Is there anything I could help with?

[matt-smarsh]

This issue seems to be the last one preventing a drop-in replacement from jsdom. I'm using vitest & @vue/test-utils@1 and I can't switch because of the error TypeError: attributes.item is not a function which is thrown from within @vue/test-utils and is unavoidable.

[flip111]

I switched from jsdom to happy-dom for performance and jsdom lack of ESM. I can't get my nodejs program to run cross-platform without this feature.

[jledentu]

@capricorn86 Don't know if you've worked on this, otherwise I can help to write a PR.

[capricorn86]

Thank you contributing @jledentu! 🙂

There is a fix in now.

You can read more about the release here:
https://github.com/capricorn86/happy-dom/releases/tag/v7.6.0