: Garrett Smith [mailto:[EMAIL PROTECTED]
Sent: Monday, September 10, 2007 11:33 PM
To: Křištof Želechovski
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: [whatwg] Progress Events done event
On 8/27/07, Křištof Želechovski [EMAIL PROTECTED] wrote:
Remember that JavaScript is a programming
On 8/27/07, Křištof Želechovski [EMAIL PROTECTED] wrote:
Remember that JavaScript is a programming language after all. You can use a
loop to get rid of the repetitions.
Start from
var done = [load, error, abort]...
and apply the closure image.aEL(?, hPB, false) to it.
Sincerely,
Chris
Remember that JavaScript is a programming language after all. You can use a
loop to get rid of the repetitions.
Start from
var done = [load, error, abort]...
and apply the closure image.aEL(?, hPB, false) to it.
Sincerely,
Chris
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL
This proposal is similar to the callbacks that Prototype's
Ajax.Requestmakes available. Instead of a done event, it provides
the callback
onComplete: http://prototypejs.org/api/ajax/options
On 8/26/07, Garrett Smith [EMAIL PROTECTED] wrote:
I've noticed a case when developing Ajax apps that I
On 8/26/07, Weston Ruter [EMAIL PROTECTED] wrote:
This proposal is similar to the callbacks that Prototype's Ajax.Request
makes available. Instead of a done event, it provides the callback
onComplete: http://prototypejs.org/api/ajax/options
Thanks!
This is evidence of a real-world use case
On Sat, 25 Aug 2007, Garrett Smith wrote:
I've noticed a case when developing Ajax apps that I often end up
duplicating a call to hide loading.gif (for example) when the call
is over.
Progress Events
- Original Message -
From: Garrett Smith [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Saturday, August 25, 2007 11:24 PM
Subject: [whatwg] Progress Events done event
I've noticed a case when developing Ajax apps that I often end up
duplicating a call to hide
