Walter Lee Davis wrote:
> Aha. Try using onComplete. onSuccess fires when the Ajax event returns
> success (naturally) but before you've done anything in the local DOM
> with your new content. It's the Ajax equivalent of a 200 header from
> the browser. All it means is "everything worked, no
Jason Frisvold wrote:
> I actually tried onSuccess before, and had the same results. Is this
> the correct syntax?
onComplete makes this work properly. So, I wonder, if I properly check
for failures, is it ok to use onComplete for this?
--
---
Jason Frisvold
xenopha...
Aha. Try using onComplete. onSuccess fires when the Ajax event returns
success (naturally) but before you've done anything in the local DOM
with your new content. It's the Ajax equivalent of a 200 header from
the browser. All it means is "everything worked, now your content is
coming!"
Wa
T.J. Crowder wrote:
> Hi,
>
> Ajax.Updater is (by default) *asynchronous*, so your code doing the
> resizing runs before the request completes. Use an onSuccess handler
> [1] instead. (Don't just make the request synchronous, it locks up
> the browser UI.) You might also find the "bulletproof
Hi,
Ajax.Updater is (by default) *asynchronous*, so your code doing the
resizing runs before the request completes. Use an onSuccess handler
[1] instead. (Don't just make the request synchronous, it locks up
the browser UI.) You might also find the "bulletproof ajax requests"
page[2] on the un
