Closed Bug 12498 Opened 21 years ago Closed 11 years ago

xpconnect needs to be able to deal with the new JS 'Error' exceptions

Categories

(Core :: XPConnect, defect, P2)

x86
Windows NT
defect

Tracking

()

RESOLVED INCOMPLETE
Future

People

(Reporter: jband_mozilla, Unassigned)

Details

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.
Status: NEW → ASSIGNED
Moving all XPConnect QA contact to rginda
QA Contact: cbegle → rginda
Target Milestone: --- → Future
mass reassign of bugs to dbradley@netscape.com
Assignee: jband → dbradley
Status: ASSIGNED → NEW
Status: NEW → ASSIGNED
Priority: P3 → P5
Removing Rob as QA contact
QA Contact: rginda → pschwartau
Priority: P5 → P2
QA Contact: pschwartau → xpconnect
Assignee: dbradley → nobody
Whiteboard: [expired?]
Status: ASSIGNED → NEW
->INCOMPLETE (and this is *highly* unlikely to still be an issue... I hope)
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INCOMPLETE
Whiteboard: [expired?]
You need to log in before you can comment on or make changes to this bug.