Click, touch, load, drag, change, input, error, resize — the list of possible DOM events is lengthy. Events can be triggered on any part of a document, whether by a user’s interaction or by the browser. They don’t just start and end in one place; they flow though the document, on a life cycle of their own. This life cycle is what makes DOM events so extensible and useful. As developers, we should understand how DOM events work , so that we can harness their potential and build engaging experiences. Throughout my time as a front-end developer, I felt that I was never given a straight explanation of how DOM events work. My aim here is to give you a clear overview of the subject, to get you up to speed more quickly than I did. I will introduce the basics of working with DOM events, then delve into their inner workings, explaining how we can make use of them to solve common problems. Listening For Events In the past, browsers have had major inconsistencies in the way they attach