[whatwg/dom] Editorial: improve clarity in event dispatch model`` (#645)

In https://bugzilla.mozilla.org/show_bug.cgi?id=1449560#c5 @bzbarsky wrote:

> In particular, the fact that the "target" in the dispatch algorithm becomes the "item" in the event path structs.

I'd welcome ideas on how to improve this. I agree it's a bit of a mess, but I also don't quite see how to make things substantially better. We could rename to "item" to "current target" perhaps, but I'm not sure if that helps or hurts things.

> I _really_ hope "the last tuple in event’s path whose target is non-null" is in fact the thing that we are thinking of as the target of the event... Is it?

It's the outermost target. The innermost target (the one passed to dispatch) will be the first tuple in event's path whose target is non-null.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/645