On 1/31/11 6:19 PM, Zack Weinberg wrote:
It seems like that code is already doing almost what it needs to, though. For the exception we've been kicking around, it fabricates a DOMException object with separate properties for the location, line number, error code name, and error message.
No, XPConnect takes such an object as _input_. Then it converts it to a string and throws that string to JS, iirc. Yes, this is absolutely dumb... and maybe I'm misremembering. But something stupid like that happens.
The real problem as I see it is that the error console (and the "web console") don't break the exception down appropriately
They do if you hand them an exception with something other than just a string in it.
-Boris _______________________________________________ dev-tech-layout mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-layout
