Skip to main content

Quick Event-Handling Suggestion

Today I had to rewrite how some events were being handled in an application. One of the advantages often cited when using DOM level 2 event handling (use of attachEvent or addEventListener) is that you can add multiple handlers for the same event type on the same element. While I do not deny this to be an advantage (I will soon explain why), I feel that this practice should generally be avoided. A couple reasons, 1.) browsers do no guarantee what order the events get fired in (see here) 2.) Even if you're using a framework that ensures the events are fired in a specific order, you may still run into issues with how one handler should possibly not be fired due to certain circumstances.

When do you make use of multiple handles for the same type/element pair? I would say generally only when the events are between separate objects. To keep things modular, it is best to let each object/class handle the events by itself rather than trying to make some super handler.


Popular posts from this blog

Quick Setup Using JSPM

Cross post from my employer's development blog:
Want to use JSPM rather than Bower for running the example? Follow these steps. This is basically a duplicate of the [Getting Started tutorial][tutorial] on the [ website][website] but using a really simple JSPM setup. This is a very crude guide where I list everything I had to do to get things running.

Create an empty project folder npm install Copy server code verbatim from the Getting Started guide jspm install Hit enter for all the prompts from JSPM

We’re going to modify the client side code a little bit. We have native support for ES6 compiling with JSPM/Babel so we can import the Deepstream client directly:

import deepstream from ''; let ds = deepstream( 'localhost:6020' ).login();

let record = ds.record.getRecord( 'someUser' );

let input = document.querySelector( 'inp…

Atari E3 2004 PAL digital press kit

Making note of some old swag. The Atari E3 2004 PAL digital press kit. See video for details.

Changing Password Requirements with SailsJS and Passport

Cross post from my employer's development blog:

If you perform an installation of [Passport][passport] with [SailsJS][sails] using the [Sails Passport Auth Generator][sails-generate-auth] you get several files in your app already configured for you. If you then use passport-local, you will already have a complexity requirement on the password. It defaults to requiring 8 characters minimum, letters, numbers, and symbols.

What if you want to change this requirement? In the generated model file `Passport.js`, you should see a line that says `provider   : { type: 'alphanumericdashed' },` and `password    : { type: 'string', minLength: 6 }`. The minLength is an easy and obvious change. What about the complexity requirement though? This stumped me for a bit. There doesn’t seem to be any mention of these keywords or providers on the Passport official site, nor anything in the [Passport-local repository][passport…