Stoping the big event flow as well as other like events on an equivalent target playing with stopImmediatePropagation()

Calling stopProgagation() from within an event handler/listener will stop the capture and bubble event flow phases, but any events directly attached to the node or object will still be invoked. In the code below the onclick event attached to the is never gets invoked because we are stopping the event from bubbling up the DOM when clicking on the

.

Notice that other click events attached to the the

still get invoked! Additionally using stopPropagation() does not prevent default events. Had the

in our code example been a with an href value calling stopPropagation would not have stopped the browser default events from getting invoked.

Calling the stopImmediatePropagation() from within an event handler/listener will stop the event flow phases (i.e. stopPropagation()), as well as any other like events attached to the event target that are attached after the event listener that invokes the stopImmediatePropagation() method. In the code example below If we call stopImmediatePropagation()from the second event listener attached to the

the click event that follows will not get invoked.

With the stopImmediatePropagation() does not end default situations. Browser default incidents still score invoked and only getting in touch with preventDefault() will minimize this type of incidents.

Custom events

A designer is not restricted to the fresh new predetermined experiences items. Its possible to add and you can invoke a custom knowledge, by using the addEventListener() method including typical for the combiniation with document.createEvent(), initCustomEvent(), and you may dispatchEvent(). Throughout the code less than We manage a custom made experience entitled goBigBlue and you can invoke one experience.

Cards

The fresh new DOM cuatro specifiction extra a good CustomEvent() constructor that has simplified the life span cycle off a customized enjoy however, it’s just not supported in ie9 and also as with the writting and is however inside the flux

Simulating/Leading to mouse occurrences

Simiulating an event is not unlike creating a custom event. In the case of simulating a mouse event we create a ‘MouseEvent’ using document.createEvent(). Then, using initMouseEvent() we setup the mouse event that is going to occur. Next the mouse event is dispatched on the element that we’d like to simulate an event on (i.e the

in the html document). In the code below a click event is attached to the

in the page. Instead of clicking the

to invoke the click event the event is triggered or simulated by programatically setting up a mouse event and dispatching the event to the

.

Notes

Simulating/causing mouse incidents only at that creating really works in all modern web browsers. Simulating most other experiences systems quickly grows more difficult and you will leveraging replicate.js otherwise jQuery (e.g. jQuery end up in() method) becomes neccsary.

Knowledge delegation

Event delegation, stated simply, is the programmatic act of leveraging the event flow and a single event listener to deal with multiple event targets. A side effect of event delegation is that the event targets don’t have to be in the DOM when the event is created in order for the targets to respond to the event. This is of course rather handy when dealing with XHR responses that update the DOM. By implementing event delegation new content that is added to the DOM post JavaScript load parsing can immediately start responding to events. Imagine you have a table with an unlimited number of rows and columns. Using event delegation we can add a single event listener to the

node which acts as a delegate for the node or object that is the initial target of the event. In the code example below, clicking any of the

‘s (i.e. the target of the event) will delegate its event to the click listener on the

. Don’t forget this is all made possible because of the event flow and in this specific case the bubbling phase.

Author