Click handler running just once

[nmeri17]

@m3g4p0p

the important part is that you can access the element that triggered the event with event.target, from where the event bubbles up to the element to which the listener was actually attached. So in the actual addEventListener() callback, this would refer to context in the above example.

I understand. I’m just not used to that type of maneuver. So according to this

@m3g4p0p

you’d just bind one single listener to the containing ul element. This is especially useful if the list can change dynamically

in a situation like this, if I had attached the handler to the parent container and ensured the handler only fired (or became potent) when the target matched class nobody, I would have saved myself the stress of porting the function all over the place? One of the major problems in that situation was the thisvehemently refused to switch contexts. I repeatedly tried calling the handler like in this implementation but it refused to work. I’m still too traumatised by that episode to reattempt reviving the dilemma using this current solution.