Faq on JS Errors

[MC]

Thats a nice FAQ but it doesn't really help too much. How would you capture
js errors after the page has loaded? If I knew that, I could send them back
to a server via ajax and record them, so they could be fixed.

Any ideas on that?
MC

 

[Peter Michaux]

Thats a nice FAQ

Which FAQ?

but it doesn't really help too much. How would you capture
js errors after the page has loaded? If I knew that, I could send them back
to a server via ajax and record them, so they could be fixed.

This is not a frequent question.

Any ideas on that?

try-catch

Peter

 

[MC]

Which FAQ?


This is not a frequent question.


try-catch

Peter

So there is no error stack that I can access?
Something like document.error[0]....?
MC

 

[Peter Michaux]

Which FAQ?

This is not a frequent question.

Peter

So there is no error stack that I can access?
Something like document.error[0]....?

There is an (Java) error stack available in Rhino.

http://www.mozilla.org/rhino/

Peter

 

[slebetman]

Thats a nice FAQ but it doesn't really help too much. How would you capture
js errors after the page has loaded? If I knew that, I could send them back
to a server via ajax and record them, so they could be fixed.

Try handling the error event:

window.onerror = function (err,url,lineNumber) {
sendByAjax(err+", at:"+url+", line:"+lineNumber);
}

see:

http://developer.mozilla.org/en/docs/DOM:window.onerror

 

[Thomas 'PointedEars' Lahn]

Try handling the error event:

window.onerror = function (err,url,lineNumber) {
sendByAjax(err+", at:"+url+", line:"+lineNumber);
}

see:

http://developer.mozilla.org/en/docs/DOM:window.onerror

The onerror event handler is proprietary and unreliable. Therefore it
should only serve as a fallback for exception handling.

It should also be noted that syntax errors cannot be handled either way.


PointedEars