> ou! the complete handler... perhaps it just needs a little more
> documentation? Or did I miss it?
It's documented on $.ajax...
(Function) error - A function to be called if the request fails. The
function gets passed two arguments: The XMLHttpRequest object and a
string describing the
ou! the complete handler... perhaps it just needs a little more
documentation? Or did I miss it?
On 10/13/06, Steven Wittens <[EMAIL PROTECTED]> wrote:
>
> > Yup! I noticed that too. It broke a few pages, and scared me into
> > DEBUGGING mode, I always liked getting back the whole httpreq.
>
>
Steven -
This is all an excellent point - and something that I regret doing.
I've posted your notes on the jQuery blog, explaining the situation to everyone.
http://jquery.com/blog/2006/10/13/minor-api-change-in-102/
Thanks again.
--John
On 10/13/06, Steven Wittens <[EMAIL PROTECTED]> wrote:
>
> Yup! I noticed that too. It broke a few pages, and scared me into
> DEBUGGING mode, I always liked getting back the whole httpreq.
Well you can still use the "complete" handler to get the
XMLHttpRequest back, but that handler fires regardless of success or
failure. You'd have to check the s
Yup! I noticed that too. It broke a few pages, and scared me into
DEBUGGING mode, I always liked getting back the whole httpreq.
On 10/13/06, Steven Wittens <[EMAIL PROTECTED]> wrote:
> It seems that the 'success' callback of $.ajax was changed to accept
> as its first argument the actual parsed d
It seems that the 'success' callback of $.ajax was changed to accept
as its first argument the actual parsed data rather than the xmlHttp
object, in 1.0.2? This behaviour broke several Drupal features when I
upgraded it to jQuery 1.0.2...
We should really avoid such API changes in the future
