This tutorial is for Dojo 1.6 and may be out of date.

Up to date tutorials are available.

Events with Dojo

In this tutorial, we will be exploring dojo.connect and how Dojo makes it easy to connect to DOM events as well as custom events on native objects. We will also explore Dojo's publish/subscribe framework.

Getting Started

Much of your JavaScript code will be preparing for events: both responding to and generating new events. This means that the key to building responsive, interactive web applications is creating effective event connections. Event connections allow your application to respond to user interaction and wait for actions to happen. In a browser context, we have DOM events, but we can also think of function calls as events: "when this happens, do this". That is the job of Dojo's main event workhorse: dojo.connect.

DOM Events

You might be asking yourself, "Doesn't the DOM already provide a mechanism for registering event handlers?" It does, but not all browsers follow the DOM specifications: between all of the DOM implementations from the major browsers there are three (3) ways to register event handlers (addEventListener, attachEvent, and DOM0). Add to that two different event object implementations and one browser that fires registered functions in "random order" and causes memory leaks when registering event handlers and you have a recipe for disaster.

Thankfully, Dojo normalizes the way you work with DOM events: it irons out the differences between DOM APIs and prevents memory leaks with one API: dojo.connect. Let's say we have the following markup:

<button id="myButton">Click me!</button>
<div id="myDiv">Hover over me!</div>

Let's also imagine that you want the div to change to blue when you click the button, red when you hover over it, and back to white when you're done hovering. dojo.connect makes that very simple:

var myButton = dojo.byId("myButton"),
	myDiv = dojo.byId("myDiv");

dojo.connect(myButton, "onclick", function(evt){, "backgroundColor", "blue");
dojo.connect(myDiv, "onmouseenter", function(evt){, "backgroundColor", "red");
dojo.connect(myDiv, "onmouseleave", function(evt){, "backgroundColor", "");

This example illustrates the common pattern: dojo.connect(element, event name, handler). Or, put another way, for this event on this element, connect this handler. This pattern applies to all window, document, node, form, mouse, and keyboard events. Note that in the examples shown here we include the "on" prefix in our event names. This is not required, and Dojo will normalize this parameter as necessary for each browser.

The dojo.connect method not only normalizes the API to register events, but it also normalizes how event handlers are called:

  • Event handlers are always called in the order they are registered.
  • They are always called with an event object as their first parameter.
  • The event object will have a .target property, a stopPropagation method, and a preventDefault method.

Much like the DOM API, Dojo provides a way to unregister, or disconnect, an event handler: dojo.disconnect. The return value of dojo.connect is a handle that can be passed to dojo.disconnect to stop an event handler from running. For example, if you wanted to have a one-time only event, you could do something like this:

var handle = dojo.connect(myButton, "onclick", function(evt){
	// Disconnect this event using the handle

	// Do other stuff here that you only want to happen one time
	alert("This alert will only happen one time.");

One last thing to note: dojo.connect takes an optional argument that can be inserted before the handler argument to specify the scope in which to run the handler. Without this parameter, event handlers will run with their scope set to the node passed in the first argument. This argument is very helpful when working with object methods like in widgets:

var myScopedButton1 = dojo.byId("myScopedButton1"),
	myScopedButton2 = dojo.byId("myScopedButton2"),
	myObject = {
		id: "myObject",
		onClick: function(evt){
			alert("The scope of this handler is " +;

// This will alert "myScopedButton1"
dojo.connect(myScopedButton1, "onclick", myObject.onClick);
// This will alert "myObject" rather than "myScopedButton2"
dojo.connect(myScopedButton2, "onclick", myObject, "onClick");
View Demo

When a scope object is passed, the handler argument can either be a string specifiying the method name of the scope object or an actual function object. The last line of the last example could have been written dojo.connect(myDiv, "onclick", myObject, myObject.onClick);. If the handler argument is a string, it must be the case-sensitive name of the method of the scope object; Dojo does not (and cannot) normalize this argument since it is a reference to a method of an object.

NodeList events

As mentioned in the previous tutorial, dojo.NodeList provides a way to register events to multiple nodes: the connect method. This method follows the same pattern as dojo.connect without the first argument (since the nodes in the dojo.NodeList are the objects you are connecting to). Let's look at a more advanced example than before:

<button id="button1" class="clickMe">Click me</button>
<button id="button2" class="clickMeAlso">Click me also</button>
<button id="button3" class="clickMe">Click me too</button>
<button id="button4" class="clickMeAlso">Please click me</button>
var myObject = {
	id: "myObject",
	onClick: function(evt){
		alert("The scope of this handler is " +;
dojo.query(".clickMe").connect("onclick", myObject.onClick);
dojo.query(".clickMeAlso").connect("onclick", myObject, "onClick");

Don't forget that you can also use the event name as a method as long as it is a common event name: .onclick(handler) or .onclick(scope, handler or method name). There is one disadvantage to using this method for event handler registration: there is no way to disconnect the handlers registered. dojo.NodeList.connect returns the dojo.NodeList for easy chaining rather than a list of handles to use with dojo.disconnect. If you don't foresee yourself needing to disconnect your event handlers, you can safely use the connect method.

View Demo

Object Methods

As mentioned before, dojo.connect is the workhorse of events in Dojo. This includes native objects as well. For native objects, however, you can think of methods as events. Let's say there is a button on a page and we have an object in JavaScript that will represent (or wrap) that button:

<button id="myButton">My button</button>
	var myButtonObject = {
		onClick: function(evt){
			alert("The button was clicked");
	dojo.connect(dojo.byId("myButton"), "onclick", myButtonObject, "onClick");

Let's also imagine that in another bit of code we would like to be notified when that button is clicked. Rather than adding another event handler to the button's DOM node, we can connect to myButtonObject's onClick function:

dojo.connect(myButtonObject, "onClick", function(evt){
	alert("The button was clicked and 'onClick' was called");

It must be noted that when working with native objects, no normalization is done on the event name (second) argument. Another more useful caveat is that any arguments passed to the original method are passed to the handlers:

var myButtonObject2 = {
	onClickHandler: function(evt){
		this.onClick(evt, "another argument");
	onClick: function(){}
dojo.connect(dojo.byId("myButton2"), "onclick",
	myButtonObject2, "onClickHandler");
dojo.connect(myButtonObject2, "onClick", function(evt, another){
	alert("The button was clicked, we were given a second argument: " + another);

Since event handlers for DOM nodes are only given one argument, event handlers registered with dojo.connect are only called with one argument; event handlers registered for native objects will be called with as many arguments as are passed to the original method. Other than these two caveats mentioned, dojo.connect works the same for DOM nodes and native objects.

Connecting to native object methods might not seem useful right now, but later on we will start to work with widgets and this technique will be increasingly useful. Another application for this technique is with effects; we will dive deeper into effects in a later tutorial, but we'll touch on them now for a more concrete example:

<button id="fadeButton">Fade block out</button>
<div id="fadeTarget" class="red-block"></div>
    var fadeButton = dojo.byId("fadeButton"),
        fadeTarget = dojo.byId("fadeTarget");

    dojo.connect(fadeButton, "onclick", function(evt){
        var anim = dojo.fadeOut({ node: fadeTarget });

        dojo.connect(anim, "onEnd", function(){
            alert("The fade has finished");
View Demo

For our purposes, know that dojo.fadeOut returns an object with an onEnd method that runs when the effect is done. Using what we just learned about dojo.connect and native objects, we connect to the object's onEnd method to alert the user that the animation has finished. In this case, as soon as the red block has faded out, our function will run.


All of the examples up until this point have used a created object (a DOM node, a "widget", and an effect object) as an event producer that you register with to know when something happens. But what do you do if you don't have a handle to an object or don't know if an object has been created? This is where Dojo's publish and subscribe (pub/sub) framework comes in. Pub/sub allows you to register a handler for (subscribe to) a "topic" (which is a fancy name for an event that can have multiple sources, represented as a string) which will be called when the topic is published to.

Let's imagine that in an application that we're developing, we want certain buttons to alert the user of an action; we don't want to write the routine to do the alerting more than once, but we also don't want to make a wrapping object that will register this small routine with the button. Pub/sub can be used for this:

<button id="alertButton">Alert the user</button>
<button id="createAlert">Create another alert button</button>

	var alertButton = dojo.byId("alertButton"),
		createAlert = dojo.byId("createAlert");

	dojo.connect(alertButton, "onclick", function(evt){
		// When this button is clicked,
		// publish to the "alertUser" topic
		dojo.publish("alertUser", ["I am alerting you."]);
	dojo.connect(createAlert, "onclick", function(evt){
		// Create another button
		var anotherButton = dojo.create("button", {
			innerHTML: "Another alert button"
		}, createAlert, "after");

		// When the other button is clicked,
		// publish to the "alertUser" topic
		dojo.connect(anotherButton, "onclick", function(evt){
			dojo.publish("alertUser", ["I am also alerting you."]);

	// Register the alerting routine with the "alertUser"
	// topic.
    dojo.subscribe("alertUser", function(text){
View Demo

One useful advantage to this pattern of events is that now our alerting routine can be tested in a unit test without the need to create any DOM objects: the routine is decoupled from the event producer. There are a few things to note about pub/sub:

  • dojo.subscribe can be called similarly to dojo.connect (dojo.subscribe(topic, handler) or dojo.subscribe(topic, scope, handler or method name)).
  • The second argument to dojo.publish must be an array and the items in that array will be the arguments to topic's handler functions.
  • dojo.subscribe returns a handle that can be used with dojo.unsubscribe to deregister a handler from a topic (much like dojo.connect and dojo.disconnect).


Dojo's event system is quite powerful, while being fairly simple to use. The dojo.connect method normalizes events between the DOM and native objects while also normalizing inconsistencies between browsers. Dojo's pub/sub framework gives developers a way to easily decouple event handlers from the event producers. Take time to familiarize yourself with these tools — they will be a valuable asset in creating web applications.