Closed Bug 1257892 Opened 4 years ago Closed 4 years ago
Fix the propagation of ns
IExceptions out of JS-implemented XPCOM things
This is silly. Say a JS-implemented XPCOM thing throws an nsIException (e.g. via throw Components.Exception(stuff)). We land in nsXPCWrappedJSClass::CheckForException which calls XPCConvert::JSValToXPCException. This tries to check the value for being an nsIException, but only considers XPCWrappedNatives. So we end up taking the XPCWrappedJS codepath instead of finding our already-existing exception.
Assignee: nobody → bzbarsky
Status: NEW → ASSIGNED
Attachment #8732238 - Flags: review?(bobbyholley) → review+
You need to log in before you can comment on or make changes to this bug.