jQuery .mousedown() Method

What You’ll Learn

The .mousedown() method is jQuery’s legacy shorthand for binding and triggering the mousedown event. This tutorial covers .mousedown(handler) since 1.0, .mousedown(eventData, handler) since 1.4.3, no-argument .mousedown() as a trigger, migration to .on("mousedown") and .trigger("mousedown"), and why the binding form is deprecated since jQuery 3.3. For the modern mousedown event API, see the jQuery mousedown event tutorial.

Introduction

Before jQuery 1.7 unified events with .on() and .off(), every common event had a matching shorthand — .click(), .mousedown(), .keydown(), and dozens more. The .mousedown() method let you bind a handler in one short call: $("#handle").mousedown(function(){ ... }). It remains in jQuery 3.x for backward compatibility but is marked deprecated.

Understanding .mousedown() matters when reading older drag-and-drop code, drawing tools, and legacy tutorials. The method does two distinct jobs: with a function argument it binds; with no arguments it triggers. Modern jQuery splits those roles explicitly — .on("mousedown", handler) for binding and .trigger("mousedown") for firing. This page documents the shorthand API and shows how to migrate.

Understanding the .mousedown() Method

The official jQuery API describes .mousedown() as a way to bind an event handler to the mousedown event, or trigger that event on an element. When you pass a handler, jQuery registers it on each matched element and calls it when the user presses a mouse button while the pointer is over that element — the same mousedown event that .on("mousedown") handles today.

When you call .mousedown() with no arguments, jQuery synthetically fires the mousedown event on each matched element. Bound handlers run immediately. This trigger behavior is equivalent to .trigger("mousedown").

📝 Syntax

The .mousedown() method has three signatures from the official jQuery API. The binding forms are deprecated; the trigger form remains valid but .trigger("mousedown") is preferred:

1. Bind a handler — .mousedown( handler ) (since 1.0, deprecated 3.3)

.mousedown( handler )

• handler — function executed each time mousedown fires: function( event ) { ... }.
• Returns the jQuery object for chaining.
• Modern replacement: .on( "mousedown", handler ).

2. Bind with eventData — .mousedown( [eventData], handler ) (since 1.4.3, deprecated 3.3)

.mousedown( [eventData], handler )

• eventData — optional object available in the handler as event.data.
• Modern replacement: .on( "mousedown", eventData, handler ).

3. Trigger the event — .mousedown() (since 1.0)

.mousedown()

• No arguments — triggers mousedown on every matched element.
• Runs bound mousedown handlers.
• Preferred replacement: .trigger( "mousedown" ).

Official jQuery API migration note

// Deprecated binding
$( "#target" ).mousedown( function() {
  alert( "Handler for `mousedown` called." );
} );

// Modern binding
$( "#target" ).on( "mousedown", function() {
  alert( "Handler for `mousedown` called." );
} );

// Deprecated trigger
$( "#target" ).mousedown();

// Modern trigger
$( "#target" ).trigger( "mousedown" );

Return value

• All .mousedown() signatures return the original jQuery object for chaining.
• Handler return values are ignored unless you use return false (equivalent to preventDefault() + stopPropagation()).

Examples Gallery

Five examples cover binding, eventData, triggering, migration from .mousedown() to .on("mousedown"), and press-time active states. Use the Try-it links to run each snippet in the browser. Remember: binding with .mousedown(handler) is deprecated — these demos show legacy syntax you will encounter in older code.

$( "#target" ).mousedown( function() {
  $( "#out" ).text( "Handler ran via .mousedown(function(){ ... })." );
} );

User presses mouse on #target → handler runs

#out text updates on press — before release

Deprecated — prefer .on("mousedown", fn) for new code

$( ".tool" ).mousedown( { mode: "draw" }, function( event ) {
  var tool = $( this ).data( "tool" );
  $( "#out" ).text(
    "Tool: " + tool + " | eventData.mode: " + event.data.mode
  );
} );

Press Pen → "Tool: pen | eventData.mode: draw"

Press Brush → "Tool: brush | eventData.mode: draw"

Same handler, shared eventData on every .tool button

var count = 0;

$( "#target" ).mousedown( function() {
  count++;
  $( "#out" ).text( "Target handler fired (count: " + count + ")" );
} );

$( "#fire" ).click( function() {
  $( "#target" ).mousedown();
} );

Press #target directly → count increments

Click #fire → $("#target").mousedown() → same handler runs

No-arg .mousedown() is trigger shorthand — prefer .trigger("mousedown")

$( "#legacy" ).mousedown( function() {
  $( "#out" ).text( "Legacy: .mousedown(function(){ ... }) — deprecated since jQuery 3.3." );
} );

$( "#modern" ).on( "mousedown", function() {
  $( "#out" ).text( "Modern: .on('mousedown', function(){ ... }) — use this for new code." );
} );

Press #legacy → legacy deprecation message

Press #modern → modern .on("mousedown") message

Behavior is identical — only the API name differs

$( "#handle" )
  .mousedown( function( event ) {
    if ( event.which !== 1 ) return;
    $( this ).addClass( "active" );
    $( "#out" ).text( "Pressed — .active added via .mousedown()." );
    $( document ).one( "mouseup", function() {
      $( "#handle" ).removeClass( "active" );
      $( "#out" ).text( "Released — .active removed on mouseup." );
    } );
  } );

Left-press #handle → .active class added immediately

Release anywhere → .active removed on document mouseup

Right-click ignored (event.which !== 1)

🚀 Common Use Cases

• Reading legacy code — recognize $("#handle").mousedown(fn) as equivalent to .on("mousedown", fn) in older drag libraries.
• Drawing tools — legacy canvas code often uses .mousedown(fn) to start strokes — migrate to .on("mousedown", fn).
• Proxy triggers — $("#btn").click(function(){ $("#target").mousedown(); }) — replace inner no-arg .mousedown() with .trigger("mousedown").
• Shared eventData — $(".tool").mousedown({ mode: "draw" }, fn) passes metadata without closures.
• Press feedback — add active classes on .mousedown(fn), remove on document mouseup.
• Automated testing — test suites may call .mousedown() to simulate press — consider .trigger("mousedown") for explicit intent.

📝 Notes

• Deprecated since jQuery 3.3 — do not use .mousedown(handler) or .mousedown(eventData, handler) in new code. Use .on("mousedown") instead.
• Bind with .mousedown(handler) since jQuery 1.0; eventData form since 1.4.3.
• No-argument .mousedown() triggers the event since jQuery 1.0 — prefer .trigger("mousedown").
• .mousedown() does not support event delegation — use .on("mousedown", selector, fn) for dynamic handles.
• Remove handlers with .off("mousedown") — not by calling .mousedown(undefined).
• Legacy code using .mousedown() still runs in jQuery 3.x — migrate when you refactor those files.
• For the full modern mousedown event guide — event.which, comparison with click, and drag patterns — see the jQuery mousedown event tutorial.

💡 Best Practices