Pixel Pete saysThe old way to handle events was inline onclick attributes or el.onclick properties.
Early DHTML wired events two ways: inline (<button onclick="go()">) or via the property (el.onclick = fn). Both work but allow only one handler per event — assigning a new onclick overwrites the old. They also mix behavior into markup. They were superseded by addEventListener, which allows many handlers.
Power-ups you unlock
Inline onclick="…" or el.onclick = fn
Only one handler per event
New assignment overwrites the old
Mixes behavior into markup
Quirks Mode attacks — common mistakes
Inline handlers scattering JS through HTML
Overwriting an existing onclick by accident
Expecting multiple onclick assignments to stack
Boss battleWire a click with el.onclick, then note why a second assignment replaces it.