From 024ff87014e085f354628df65db978339963b737 Mon Sep 17 00:00:00 2001 From: Dave Mayo Date: Mon, 15 Oct 2012 14:15:31 -0400 Subject: [PATCH] fixes #52 - language taken from http://dev.api.jquery.com/deferred.reject/ --- entries/deferred.progress.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/entries/deferred.progress.xml b/entries/deferred.progress.xml index 57d84a7c..a554dfad 100644 --- a/entries/deferred.progress.xml +++ b/entries/deferred.progress.xml @@ -11,7 +11,7 @@ Add handlers to be called when the Deferred object generates progress notifications. -

The argument can be either a single function or an array of functions. When the Deferred generates progress notifications by calling notify or notifyWith, the progressCallbacks are called. Since deferred.progress() returns the Deferred object, other methods of the Deferred object can be chained to this one. When the Deferred is resolved or rejected, progress callbacks will no longer be called. For more information, see the documentation for Deferred object.

+

The argument can be either a single function or an array of functions. When the Deferred generates progress notifications by calling notify or notifyWith, the progressCallbacks are called. Since deferred.progress() returns the Deferred object, other methods of the Deferred object can be chained to this one. When the Deferred is resolved or rejected, progress callbacks will no longer be called, with the exception that any progressCallbacks added after the Deferred enters the resolved or rejected state are executed immediately when they are added, using the arguments that were passed to the .notify() or notifyWith() call. For more information, see the documentation for Deferred object.