Craig Longman wrote:
>
> hello,
>
> i have been trying to get our product working 100% with mozilla so we
> can finally claim to support it, and am down to just a few more issues
> to resolve. the one big one is the way the default window.onerror
> handler is called. every piece of documentation i've read so far,
> indicates that it is called with:
>
> onerror( reason, url, line );
>
> which lets us make a very useful list of errors that occur and process
> them accordingly.
>
> however, under mozilla (0.9.4 in galeon 0.12 on linux) i find that
> onerror is called with some 'event' object that seems to contain very
> little useful information about the error. the event.type is marked
> as 'error', and i might be able to extract the URL from the
> event.target member, it seems to be an HTMLDocument object (none of my
> books refer to this object either, but i'm looking). but, the most
> important piece of information is the line number at which the error
> occured, and i can't find any way of figuring that out.
> i know i must be missing something, its difficult to imagine that this
> would have changed so drastically and have LOST all that information
> that was so useful. please help me!
>
> btw, in my searches for an answer, i have seem multiple people suggest
> elsewhere that the solution is to use try/catch. although this would
> be a lovely way of doing it (much of our onerror code is to simulate
> try/catch anyway) it is also not possible, there are too many browsers
> out there that don't support try/catch for it to be a viable answer
> for anything but a limited, tightly controlled web-app.
>
> thanks!
>
> CraigL->Thx();
This is...
http://bugzilla.mozilla.org/show_bug.cgi?id=52120
This one looks quite related...
http://bugzilla.mozilla.org/show_bug.cgi?id=79133
I don't know why this problem has been on the floor so long.
John.
