When someone interacts with a webpage, the browser sends events to the relevant JavaScript code. The dblclick event happens when the user rapidly clicks twice.
When dblclick happens
The user rapidly clicks twice.
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
<button id="demo-target" type="button">Try this button</button>
<p id="event-status" role="status">Waiting for dblclick...</p>
<script>
const eventTarget = document.getElementById("demo-target");
const eventStatus = document.getElementById("event-status");
if (eventTarget) {
eventTarget.addEventListener("dblclick", (eventDetails) => {
eventStatus.textContent = "dblclick event received";
console.log(eventDetails.type, eventDetails.target);
});
}
</script>
Reading the code
The browser listens for dblclick 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.
Double-click the target; do not require this for essential actions.
Try it in your browser
Open the page, show the Console panel, and follow this test: Double-click the target; do not require this for essential actions. Then change one thing in the example and observe whether the event still fires.
Common Beginner Mistakes
- Expecting
dblclickto fire without its required user action or browser condition. - Double-click the target; do not require this for essential actions.
- Adding repeated event listeners without considering cleanup or unwanted side effects.
Key Takeaways
dblclickreports the user rapidly clicks twice.addEventListener("dblclick", ...)listens for the event on the appropriate target.- Double-click the target; do not require this for essential actions.