Community
Participate
Working Groups
Currently a page that has a javascript error (such as the page attached next) fails silently. A callback for handling this should be added so that a Browser client can handle the error in a context-appropriate way.
Bug 77611 describes the spot where this can likely be hooked in IE.
Created attachment 22334 [details] a test page with a javascript error
I cannot find Gecko api for this. I also notice that Mozilla and Firefox don't show errors in their status bars like IE does, so I suspect that this is not currently supported. I have not investigated WebKit support.
*** Bug 272680 has been marked as a duplicate of this bug. ***
*** Bug 286480 has been marked as a duplicate of this bug. ***
Comment 0 lists only JavaScript errors, but there are additional sources of errors (and perhaps warnings) which a client of Browser might want to react to, for example: - HTTP Protocol errors (for examples see bug 272680 and bug 286480) - Security warnings or errors (invalid certificate, mixed https/http content) - Other runtime error dialogs, I'll attach a screenshot of one.
Created attachment 152100 [details] screenshot of stack overflow error
Created attachment 152101 [details] snippet that causes the stack overflow error Just for fun, I tried to find out how many recursive calls you can make back and forth between Java and JavaScript. Haven't tried it on the Mac or on Linux.
Created attachment 218815 [details] attaching some work here so it's not lost