[Seaside-dev] Issue 95 in seaside: Debugging errors in ajax callbacks not very accessible

[codesite-noreply at google.com]

Issue 95: Debugging errors in ajax callbacks not very accessible
http://code.google.com/p/seaside/issues/detail?id=95

Comment #7 by jfitzell:
In Seaside 2.9 it now works like this:

+ If you are using WADebugErrorHandler, you will get a debugger popping up  
on Ajax
requests, just like any other request
+ If you are using WACallbackErrorHandler, it will now notice that the  
request is an
Ajax request and pop up the debugger instead of return the walkback in the  
response
as it would for a normal request.

+ If you are using a non-development error handler, you will simply get an  
error
response, just like you would with a normal request. These requests will  
have an HTTP
response code of 500 (Internal Error) and should therefore be detectable  
client-side
by Scriptaculous' #onFailure:

I think that satisfies the need here...


Issue attribute updates:
	Status: Fixed
	Owner: jfitzell
	Cc: renggli

-- 
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings