On 1/28/11 7:33 PM, Zack Weinberg wrote:
We could put that information into the DOM exception, couldn't we?
Not without major surgery. Right now, what we have to work with is an nsresult.
And pull it back out and log it if and only if the exception is not caught.
If we put the info in the DOM exception somehow, I'd think just the normal uncaught exception reporting would report everything that's needed.
(While I'm complaining, this isn't exactly the same problem, but the error console messages we produce for uncaught JS exceptions that arise from DOM APIs are full of XPCOM jargon, so they give the impression that we're reporting some kind of internal failure rather than a bug in web page JavaScript.)
Is this just for the ones going through XPConnect goop, or also for the quickstubbed ones?
-Boris _______________________________________________ dev-tech-layout mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-layout
