FakeXHR and Event Targets about nise HOT 8 CLOSED

This was in a unit test environment setup by jest with testEnvironment: 'jest-environment-jsdom-global' set. I would expect that to behave the same as your test. I might need to dig some more. Thank you.

from nise.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

from nise.

Maybe you are able to dig up something a bit more definitive in the specs? https://xhr.spec.whatwg.org/#event-handlers

from nise.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

from nise.

OK, looked into this, and while you are right about what it should do, to me it seems like it already does! Here is a full repro showing that the test does not fail: https://runkit.com/fatso83/nise-109

That is using JSDOM, mind you, which is making it more complex and can hide actual issues. Which browser are you seeing any errors in?

from nise.

These are the references I asked for, btw:

• 2.7 https://dom.spec.whatwg.org/#interface-eventtarget
• 2.9 https://dom.spec.whatwg.org/#dispatching-events

And they basically just verify what you said. target should be set.

from nise.

Jest is using JSDOM under the covers, AFAIK, so it should do the same. I don't know if version differences should mean anything. Please report back if you do find out - bug or not :)

from nise.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

from nise.