jQuery .mouseup() Method

What You’ll Learn

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

Introduction

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

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

Understanding the .mouseup() Method

The official jQuery API describes .mouseup() as a way to bind an event handler to the mouseup 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 releases a mouse button while the pointer is over that element — the same mouseup event that .on("mouseup") handles today.

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

📝 Syntax

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

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

.mouseup( handler )

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

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

.mouseup( [eventData], handler )

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

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

.mouseup()

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

Official jQuery API migration note

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

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

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

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

Return value

• All .mouseup() 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 .mouseup() to .on("mouseup"), and a legacy mousedown + mouseup press-feedback pair. Use the Try-it links to run each snippet in the browser. Remember: binding with .mouseup(handler) is deprecated — these demos show legacy syntax you will encounter in older code.

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

User releases mouse on #target → handler runs

#out text updates on release — after button let go

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

$( ".control" ).mouseup( { phase: "end" }, function( event ) {
  var id = $( this ).data( "id" );
  $( "#out" ).text(
    "Control: " + id + " | eventData.phase: " + event.data.phase
  );
} );

Release Control A → "Control: a | eventData.phase: end"

Release Control B → "Control: b | eventData.phase: end"

Same handler, shared eventData on every .control trigger

var count = 0;

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

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

Release on #target directly → count increments

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

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

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

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

Press #legacy → legacy deprecation message

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

Behavior is identical — only the API name differs

$( ".btn" )
  .mousedown( function() {
    $( this ).addClass( "active" );
    $( "#out" ).text( "mousedown → .active on " + $( this ).text() );
  } )
  .mouseup( function() {
    $( this ).removeClass( "active" );
    $( "#out" ).text( "mouseup → .active removed on " + $( this ).text() );
  } );

Press Button A → .active added via .mousedown()

Release Button A → .active removed via .mouseup()

Legacy shorthand pair — prefer .on("mousedown") and .on("mouseup") for new code

🚀 Common Use Cases

• Reading legacy code — recognize $("#handle").mouseup(fn) as equivalent to .on("mouseup", fn) in older drag libraries.
• Drawing tools — legacy canvas code often uses .mouseup(fn) to finish strokes — migrate to .on("mouseup", fn).
• Proxy triggers — $("#btn").click(function(){ $("#target").mouseup(); }) — replace inner no-arg .mouseup() with .trigger("mouseup").
• Shared eventData — $(".control").mouseup({ phase: "end" }, fn) passes metadata without closures.
• Release cleanup — finish drags with .mouseup(fn) or $(document).one("mouseup", fn).
• Automated testing — test suites may call .mouseup() to simulate release — consider .trigger("mouseup") for explicit intent.

📝 Notes

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

💡 Best Practices