How to effectively attach eventListeners to DOM elements

Anonymous functions are great way to quickly get the job done, but can be a huge problem when used carelessly. It is especially when attaching eventListeners to DOM elements. Take the code below for example. Here we are attaching an eventListner to the element for the “click” event. Now, later lets say for some reason or requirement we need to remove this “click” listener.

var element = document.getElementById("my-id");
element.addEventListener("click", function() {
// handle event

After this point we don’t have any reference to this handler since we forgot to keep a reference to it hence we cannot call the removeEventListener on the element, and the function stays in the browse memory.

Now assume the same scenario with multiple elements. An appropriate example of it might be when a NxN grid of elements is created. Lets assume that the cells in the grid is being created dynamically and appended to the DOM. If these cells need to have some event handler we might end-up doing the following:

var newCell = getNewCell(); // function to create a new cell

newCell.addEventListenet("click", function() {
// handle code

This way we ended up creating NxN anonymous functions to which we don’t have references to, in case event listeners need to be removed. Even after the element does not exist in the DOM, it is the browser to decide when to remove these abandoned listeners from its memory. But as a programmer its our job to clean up the mess we created.

How to fix this:

A better approach to add eventListeners to DOM elements would be to have some kind of reference to them as below:

function myListener(event, target) {
// handle the event

var newCell = getNewCell();

newCell.addEventListener("click", myListener);

Now whenever needed, this listener can to removed from the element:

newCell.removeEventListener("click", myListener);

Sometimes, there is a requirement of firing en event listener only once (for example an init button to be clicked for initializing the application). In that case, the addEventListener method can accept an optional object parameter with a Boolean property “once” to tell the browser that this listener needs to be fired only once and after that the listener needs to be removed. So in such cases adding anonymous function as eventListeners can be considered fine (but not with multiple elements as we are still creating several anonymous functions which will sit there untill the event occurs for the first time).

myElement.removeListener("click", function() {}, {capture: false, once: true, passive: true});

So it is quite essential to take precautions when attaching anonymous functions as eventListeners especially with multiple elements.

My Favorite Programming Jokes

This time these jokes are specifically for programmers including Web Developers to System Programmers, Java guy or Python people. So here it is:

  1. I thought I would start this list with a serious note, but I didn’t know how everyone would React.
  2. Q. Why do Java guys wear specs?
    A. Because they can’t C#.
  3. Google doesn’t like straight lines, so they make Angular.
  4. Q. What do you call a snake that is approximately 3.14 units long?
    A. Python
  5. My wife asked me to go to the grocery store to get bread, and if they have eggs get twelve.So, I came with 12 bread packets and now she is mad; no idea why!!!
  6. Q.Four MySQL guys walk into a NoSQL bar but came out after some time.
    A. Because they couldn’t find a table.
  7. Q.How do programmers walk?
    void walk() {
  8. Q.Do you have any expertise in SQL?
    A. No I know No SQL.
  9. Q.How do functions break up?
    A. They stop calling each other.
  10. Duck duck = new Duck();