Right now we can end up with: ThrowErrorMessage(...); aRv.Throw(NS_ERROR_UNEXPECTED); It might be better to do this as aRv.ThrowTypeError() + aRv.ReportTypeError() or something instead. Need to think through exactly what would need to happen here and how it would make the codegen look.
In practice, this doesn't matter. No one returns anything from callbacks that would end up hitting this case anyway...
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.