James Browning

> After feedback from multiple parties, we changed EventTarget to run callbacks in the context that triggered the event (aka "dispatch context") > When there is no dispatch context (e.g....

> The idea is that the EventTarget fallback is defined through an AsyncContext variable which defaults to the empty context, but it can be set to a different snapshot. So...

> This unfortunately cuts both ways. Registration context may be what you want for some variables and some events some of the time, but (as the "feedback from multiple parties"...

> > I'm confused by how we are talking about something _generic_, and not specific to .addEventListener. The reason is because the proposed change to `.addEventListener` basically looks exactly like...

> This is my concern about composition and function coloring, where it's possible to design locally valid protocols that can't be composed, This is true of a lot of things....

> What else are you thinking of here? Basically every anti-pattern ever, just because something is an anti-pattern doesn't mean developers won't write things that way anyway. (Often because they...

I do want to point out that under the suggested change `Observable.from(asyncOrSyncIterable)` is rather strange now. In particular if you subscribe while iteration is happening you may see only a...

> ```js > // If users want to do things off-thread, e.g. to generate > // or fetch the source code asynchronously, they could run it > // in their...

> Definitely have to agree with this... It could also be a sign that `worker_threads` are "close enough" to discourage further effort there. Speaking from my own experience, the fact...

So I've been playing around with making a pull request for this, as far as the actual implementation goes it's fairly easy to [support the basics](https://github.com/inikulin/parse5/compare/master...Jamesernator:ae413f2458f3da14e8f6232dd2e013d11d304db0) however I do have...