Event Flow
Consider the situation when there are 2 elements nested together. Both have event handlers registered on the same event type, say "click". When the user clicks on the inner element, there are two possible ways to handle it:
- Trigger the elements from outer to inner (event capturing). This model is implemented in Netscape Navigator.
- Trigger the elements from inner to outer (event bubbling). This model is implemented in Internet Explorer and other browsers.
W3C takes a middle position in this struggle. Events are first captured until it reaches the target element, and then bubbled up. During the event flow, an event can be responded to at any element in the path (an observer) in either phase by causing an action, and/or by stopping the event (with method event.stopPropagation for W3C-conforming browsers and command event.cancelBubble = true for Internet Explorer), and/or by cancelling the default action for the event.
Read more about this topic: DOM Events
Famous quotes containing the words event and/or flow:
“We can glut ourselves with how-to-raise children information . . . strive to become more mature and aware but none of this will spare us from the . . . inevitability that some of the time we are going to fail our children. Because there is a big gap between knowing and doing. Because mature, aware people are imperfect too. Or because some current event in our life may so absorb or depress us that when our children need us we cannot come through.”
—Judith Viorst (20th century)
“But even suppose blood should flow. Is there not a sort of blood shed when the conscience is wounded? Through this wound a man’s real manhood and immortality flow out, and he bleeds to an everlasting death. I see this blood flowing now.”
—Henry David Thoreau (1817–1862)