What's the difference between $(form).submit and $(form).on("submit") in jQuery?

Note: .on() & .off() are the latest jQuery syntaxes at the time of writing (August 2014).

If you use jQuery 1.7 or above, methods .bind(), .delegate(), and .live() should not be used. The same applies for .unbind(), .undelegate(), & .die().

---

Introduction:

Similarly to jQuery's .on('click') vs .click() , using .on('submit') vs .submit() adds a number of advantages:

In the .on('click') vs .click() answer from andreister, he points out the memory usage being smaller, I expect the same for .on('submit') vs .submit().

But the much more significant advantages for .on('submit') vs .submit(), are some kind of "programmatical convenience":

1. Working with dynamically added elements
2. namespaces andreister also mentioned (that I pointed out in his answer's comments)

See some sample usages below to see how this all works.

---

Working with dynamically added elements: Sample usage 1

see live demo (click on Run/Clear in the top-right) on jsbin.com/puqahunovido/1/edit?html,js,console

Basically, you can tell jQuery to "observe" if a element has any of its children (direct or not) being submitted. This is particularly useful if you dynamically add new forms to this element. You then do NOT need to "re-hook" these new form to the jQuery handler.

---

Namespaces: Sample usage 1

see live demo (click on Run/Clear in the top-right) on jsbin.com/xalenefilifi/1/edit?html,js,console

/* bind form submission to 2 jQuery event handlers, each having a different namespace */
$(".js-form-hook-xyz").on("submit.hey", function() { console.log("hey!"); });
$(".js-form-hook-xyz").on("submit.hello", function() { console.log("hello!"); });

$(".js-form-hook-xyz").submit(); /* point 1: displays "hey!hello!" */

/* ... later in the code, unbind form submission for ONLY 1 handlers */
$(".js-form-hook-xyz").off("submit.hello");

$(".js-form-hook-xyz").submit(); /* point 2: displays "hey!" */

The result is that if the form is submitted at "point 1", both handlers are attached, hence called. And later on, at "point 2" handler "submit.hello" is not attached anymore so only the other handler triggers.

---

Namespaces: Sample usage 2:

see live demo (click on Run/Clear in the top-right) on jsbin.com/vubolacozuwe/1/edit?html,js,console

/* bind form submission to 2 jQuery event handlers, each having the SAME namespace */
$(".js-form-hook-xyz").on("submit.greetings", function() { console.log("Bonjour!"); });
$(".js-form-hook-xyz").on("submit.greetings", function() { console.log("Hola!"); });

$(".js-form-hook-xyz").submit(); /* point 1: displays "Bonjour! Hola!" */

/* ... later in the code, unbind form submission for ".greetings" namespace handlers */
$(".js-form-hook-xyz").off(".greetings");

$(".js-form-hook-xyz").submit(); /* point 2: displays nothing, handlers were removed */

The result is that if the form is submitted at "point 1", both handlers are attached, hence called. And later on, at "point 2" handler ".greetings" namespace handlers have been removed so nothing is displayed.

---

There might be even more cool sample usages I could think of for now so I will leave this for another time. Just look into the jQuery doc & search for similar topics on SO or Google. You'll find a bunch of interesting things I'm sure.

Resources:

1. Difference between .on('click') vs .click()
2. How to unbind a specific event handler
3. http://api.jquery.com/on/#event-names
4. api.jquery.com/on
5. api.jquery.com/submit

If you look at the jQuery .submit() docs

This method is a shortcut for .on('submit', handler)

They behave the same

As you can see in jQuery's internal code, using the shorthand version will internally call .on()

jQuery.each( ("blur focus focusin focusout load resize scroll unload click dblclick " +
    "mousedown mouseup mousemove mouseover mouseout mouseenter mouseleave " +
    "change select submit keydown keypress keyup error contextmenu").split(" "), function( i, name ) {

    // Handle event binding
    jQuery.fn[ name ] = function( data, fn ) {
        return arguments.length > 0 ?
            this.on( name, null, data, fn ) :
            this.trigger( name );
    };
});