No description provided.
(Moved from bug 243621 comment 28.)
I simply wanted to remind of the (possible) issue: please, first check if this bug is valid or not.
And the issue you're vaguely alluding to is that .returnCode is only reliably propagated through xpconnect in failure cases, not in success? Wouldn't you think that that was the point of the patch that you checked in, which changed to throw(returnCode = whatever) to get into that failure case?
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.