Does the currentEvent variable make a sense in Inner Invoke?

[dSalieri]

Now we have this:

7. Let currentEvent be undefined.
8. If global is a Window object, then:
   1. Set currentEvent to global’s current event.
   2. If invocationTargetInShadowTree is false, then set global’s current event to event.

12. If global is a Window object, then set global’s current event to currentEvent.

Can we short into this:

7. If global is a Window object, then:
   1. If invocationTargetInShadowTree is false, then set global’s current event to event.

11. If global is a Window object, then set global’s current event to undefined.

I wondered because currentEvent always has undefined value. Do we have a case when this reduction could break the logic?

[annevk]

I think you are correct that we could simplify this. Because global's current event is always initially undefined and nothing but these steps manipulate it.

This was introduced in #407. @miketaylr do you happen to recall the thinking here?

[annevk]

Oh wait. Never mind. I think this makes sense when the listener dispatches another event. In that case there will be a current event.

[dSalieri]

@annevk nested events right? In that case it make sense, you're right.

document.body.addEventListener("click", (e) => {
   e.currentTarget.dispatchEvent(new CustomEvent("hello"))
})

[miketaylr]

I think this makes sense when the listener dispatches another event. In that case there will be a current event.

Yep.