JS Error Messaging suggestions

[Java script Dude]

I am at a point of deciding on the future of how my frameworks present
errors to users.

Currently, I capture all errors with window.onerror and I create a big
ugly JavaScript dump that includes: Error message, Line number, source
file (moz), stack dump, date, url, other meta data and some contact
information.

Needless to say, it is verbose and ugly but it has as much information
as I can get to debug the issue but form a user perspective, it must be
scary.

I am now considering other options such as showing a nice floating and
clickable message that an error ocurred. Clicking may give them the
option to read the message, send the message to dev team and with
possible debugging data.

For those who are maintaining huge JS applications, what is your ideal
way of handling JS error and keeping the users in the know without
scaring them with the gory details?

Your insight is greatly appreciated.

JsD

[Joshie Surber]

> For those who are maintaining huge JS applications, what is your ideal

way of handling JS error and keeping the users in the know without
scaring them with the gory details?

I have found that the best comprimise is to create a form with all the
error information as hidden fields, display a simple message - "sorry
an error occoured" or the such - with a submit button to report it and
a message letting the user know that reporting the error will help
refine the application, maybe a couple of "what were you doing that
f**ked up my app?" type text fields.

Bonus points for submitting the form using AJAX or something else
completely invisible when possible, and displaying the button as a
fallback otherwise. Be sure to change the message about how the user
should report the error to let them know that it has already been
reported.

[Java script Dude]

> "what were you doing that f**ked up my app?"

My thoughts exactly =)

Thanks for the Info