quirksmode has more historical background and actually explains what happens during capture and bubble and when you might want to use it.<p><a href="http://www.quirksmode.org/js/events_order.html" rel="nofollow">http://www.quirksmode.org/js/events_order.html</a>
"When an event is attached to an element, it will fire once the event has fully bubbled up to the document."<p>This is not quite correct. The event will fire <i>as</i> it bubbles upward, not <i>after</i> it reaches the document level.<p>The DOM Events Level 3 specification has a helpful diagram:<p><a href="http://www.w3.org/TR/DOM-Level-3-Events/#event-flow" rel="nofollow">http://www.w3.org/TR/DOM-Level-3-Events/#event-flow</a><p>There's also the "browser default" behavior, which is stuff like highlighting selected text. That <i>does</i> happen after the event finishes bubbling. (Usually.)<p>Note that stopping an event from bubbling (with `event.stopPropagation()`) and stopping an event's default behavior (with `event.preventDefault()`) are two separate, unrelated actions. However, returning false from an event handler is equivalent to doing both.
So far, feedback has been:<p>1. maybe an initial syntax overview: target.addEventListener(type, listener[, useCapture]);<p>2. I think it’d be worth explaining what capture and bubble are.<p>I agree!