JS: DOM API
2026-02-21 02:53 Diff
https://hexlet.io/courses/js-dom/lessons/events/theory_unit

Interactive systems, such as websites in a browser or even the terminal, are arranged according to the same principle. They load, then go into a waiting mode, and wait for the user to perform an action. Such actions include clicks, typing, mouse movements, keyboard shortcuts, and so on.

From the code's perspective, there are events representing all actions. Let's observe some popular events:

  • click
  • submit
  • keyup
  • keydown
  • focus
  • contextmenu
  • mouseover
  • mousedown
  • mouseup

The events are highly detailed. Even typing a letter is split into two events: pressing the key and releasing the key. In addition, we can distinguish hotkeys from regular input with the help of the keypress event.

Any event will be associated with a specific element in the DOM. Imagine you need to add a new behavior. You should find any element and add a callback to the addEventListener() method. The program will call it when an event occurs:

Each event handler is a function that gets called when an event occurs. These handlers run one by one, following the order they were defined.

If necessary, you can delete the handler, although this is rare in practice:

We can call events programmatically. For example, this is relevant for focus.

Imagine that you open a chat hoping to write a message there, but no text appears. You need to focus on the input field to type.

By default, this doesn't happen, and this is where we come in:

How to test

You should use events in the browser regularly to understand how they work. The easiest way to do this is as follows:

  1. Open the console on any site. See where you can find the kind of elements you want to work with, such as buttons or forms
  2. Choose any element you want to practice. For simplicity's sake, you can take body
  3. Add a handler to it
  4. Call an event, and you'll see a reaction

It is how you can test any event on any site.

Event object

Each event that occurs has information associated with it, which depends on the type of event. For example, the click event involves the click and its coordinates — the point on the screen. This information is available through an event object passed to the event handler. Event objects are passed to any handler always as a single parameter:

Each click on the button will cause a new event object with its values corresponding to the current event. The event is an ordinary object filled with many properties which are easiest to learn directly in the browser. Different events have both common properties and specific ones.

For example, a click has coordinates, and a keystroke has its value. For more information about the properties, see the documentation.

General properties:

  • event.target is the DOM element where the event occurred. It's the easiest way to get the data needed after the event
  • event. type is the event's name, for example, click, keyup, and so on

As an example, let's look at the task of validating the entered password. We'll highlight the input field with a red frame if the password is too short:

See the Pen js_dom_events by Hexlet (@hexlet) on CodePen.

Default action

For some elements, the browser performs a default action when certain events are triggered. For example, if we put a handler for clicking on a link, it will suddenly take us to another page, the one specified in the href attribute.

Here we can see an example of the default action itself, which isn't affected by the presence of handlers. If you cancel this action, you should call the event.preventDefault() method inside the handler:

The following elements have default actions:

  • Clicking on a link takes you to the page specified in the href attribute
  • Clicking a Submit button starts sending the form to the server
  • Rotating the mouse wheel in textarea moves the text if it doesn't fit
  • Right-click context menu call

Competition between events

While we execute handlers, new events may occur both from user actions and automated actions from the handlers themselves. Some events always happen as a whole block — for example, mouseup and click. But this doesn't mean that the execution of the code will automatically drop everything and switch over to processing these events. Instead, events are queued and executed sequentially.

But some events are still taken into processing immediately. It applies to events that are generated programmatically, for example, focus.

You may wonder what happens to the page while we execute the handler. And there are a few possible options here.

If the handler executes some code synchronously, such as making calculations, everything else stops, and the page freezes. If this behavior lasts too long, some browsers will freeze, and others will suggest closing the tab. Here we can conclude that handlers should perform their task as soon as possible.

But what if we have a synchronous tab, such as a request being made to the server? In this case, everything works OK, since HTTP requests do not block code execution.

This lesson may make it clear why JavaScript is the way it is. The event system is possible only in asynchronous code. Essentially, when a page loads, the handlers are initialized and installed, and then, as a rule, no code is executed; the entire page waits for actions from the user.

Common mistakes

Quite often, beginners get confused about functions. Instead of the function itself, they pass the result of the function call to the handler:

The handler() function is executed when the handler is hovered over the event, instead of the function itself the result of the handler() call will be passed.