Content · Web Development · HTML

HTML change DOM Event: Reference and Examples

Learn when the change DOM event fires and how to handle it with JavaScript using a practical HTML example.

1 views Published Oct 19, 2026 Updated Oct 19, 2026 Admin

When someone interacts with a webpage, the browser sends events to the relevant JavaScript code. The change event happens when a control value has been committed.

When change happens


A control value has been committed.

You can listen for it using addEventListener(). That keeps event handling separate from HTML attributes such as onclick and works well with modern code organization.

A small working example


<label for="demo-target">Try the input</label>
<input id="demo-target" name="sample" type="text" required>
<p id="event-status" role="status">Waiting for change...</p>
<script>
    const eventTarget = document.getElementById("demo-target");
    const eventStatus = document.getElementById("event-status");

    if (eventTarget) {
        eventTarget.addEventListener("change", (eventDetails) => {
            eventStatus.textContent = "change event received";
            console.log(eventDetails.type, eventDetails.target);
        });
    }
</script>

Reading the code


The browser listens for change on the relevant target. When the event occurs, the callback receives eventDetails, updates the status message and logs the event name and target in Developer Tools.

Type then blur a text field, or change a select; differs from input.

For text fields, it normally fires after the user commits a changed value, often by moving focus away.

The form example is for learning. HTML constraint validation is helpful feedback, but the server must still validate submitted values and handle requests safely.

Try it in your browser


Open the page, show the Console panel, and follow this test: Type then blur a text field, or change a select; differs from input. Then change one thing in the example and observe whether the event still fires.

Common Beginner Mistakes


  • Expecting change to fire without its required user action or browser condition.
  • Type then blur a text field, or change a select; differs from input.
  • Adding repeated event listeners without considering cleanup or unwanted side effects.

Key Takeaways


  • change reports a control value has been committed.
  • addEventListener("change", ...) listens for the event on the appropriate target.
  • Type then blur a text field, or change a select; differs from input.
Share this resourceSend this page to someone who may find it useful.