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

One option is to rename `item` to `current target` in the dispatch structs and then rename `target` to `current target` in the algorithm that constructs them, so that the names match....

And maybe call the thing that becomes `target` in the dispatch struct `targetOverride` or `target` consistently?  Less sure about this one.

It would also help a lot if https://dom.spec.whatwg.org/#concept-event-path-append described the meaning of the members of the struct.  Right now nothing seems to do that, so you have to go dig to figure out what the difference is between the `target` and `targetOverride` arguments and when one would use one vs the other.  I _think_ the `target` argument is what will become the event's `currentTarget` when dispatching to this struct and `targetOverride`, if not null, is what retargets the event at shadow dom boundaries?  But I'm not 100% sure that's always the case even after reading through this stuff for a bit and double-checking with smaug.

-- 
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#issuecomment-387751088