Addition of "once" event handler

[bfattori]

The following code will assign an event, and then unbind that event immediately after assignment. Similar in effect to "one", however "one" will unbind all events bound to the type. "once" will only unbind the event passed.

/**
 * Similar in effect to using one() to bind an event to fire once and be
 * removed, however this will only remove the handler you assign.  Any
 * handlers already assigned to the event will not be removed as one() does.
 */
once: function(type, data, fn) {
	return this.each(function(){
		jQuery.event.add( this, type, function(event) {
			jQuery(this).unbind(event, arguments.callee);
			return (fn || data).apply( this, arguments);
		}, data);
	});
}

[bfattori]

Crap... I hate that I cannot edit my ticket! It doesn't unbind after assignment, but after execution

Sheesh... =)

[flesler]

I think this is actually a bug of jQuery, IMO one should only unbind the recently bound function.

[flesler]

bfattori's proposal

[telega]

I have one more suggestion about "one" function: currently it isn't possible to unbind function bound using one(), i.e. unbind in the following code doesn't work:

  function test() {
    alert("test");
  }
  $(document).one("click", test);
  $(document).unbind("click", test);

I guess it would be good to have the ability to unbind "one" event handlers.

[flesler]

It might also be used for jQuery.fn._toggle, mapping both (or more) functions, to the bound click handler.

[flesler]

Should fix the proxy issue, and adds a generic function for jQuery to reuse. Implemented it in jQuery.event.add.

[flesler]

$.proxy moved to $.event.proxy, merged with the 'toggle-with-n-functions' feature. proxy is implemented in toggle as well.

[flesler]

Fixed and implemented $.event.proxy at [5352]

[joern]

Fixed in [5352].

[aheimlich]

It seems that the fix for this didn't actually make it into v1.2.4, so I'd suggest changing the milestone to avoid confusing others like myself (who actually that this was fixed in v1.2.4).

[aheimlich]

Replying to aheimlich:

(who actually that this was fixed in v1.2.4).

duurrrr....

That should have been: (who actually thought that this was fixed in v1.2.4).