Robert, >> It does seem like the global events should fire *before* individual >calls, >> that way you could cancel the other events in the queue... >> > >really? i think the docs say the other way around.. i like to know how >that could be done - cancel the other events. not for the error >handling (the rule: do not check for 403 in your callback function is >easy) but for the success handling :) i'd like to examine the result >and decide to eventually cancel a html update..
I wasn't saying it *does*, I was trying to say it *should*--I just didn't would it very well. I would just see a benefit in firing off the global events first--that way you could return true to continue the event chain or return false to cancel the event chain. That would allow you to write an $.ajaxError() handler and if the return status was 403, you make the user re-login and if there error is anything else, you just return true to have it continue with any specific error handlers. -Dan
