Closed Bug 12498 Opened 21 years ago Closed 11 years ago
xpconnect needs to be able to deal with the new JS 'Error' exceptions
JS is soon to have a hierarchy of 'Error' exceptions. The xpconnect code that extracts information out of exceptions needs to be taught how to best extract information from them.
Moving all XPConnect QA contact to rginda
QA Contact: cbegle → rginda
mass reassign of bugs to firstname.lastname@example.org
Assignee: jband → dbradley
Status: ASSIGNED → NEW
Removing Rob as QA contact
QA Contact: rginda → pschwartau
QA Contact: pschwartau → xpconnect
->INCOMPLETE (and this is *highly* unlikely to still be an issue... I hope)
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.