Closed Bug 312648 Opened 20 years ago Closed 6 years ago

NS_ScriptErrorReporter uses nsIScriptError for console message

Categories

(Core :: DOM: Core & HTML, defect, P5)

x86
Windows XP
defect

Tracking

()

RESOLVED INVALID

People

(Reporter: WeirdAl, Unassigned)

References

()

Details

nsCOMPtr<nsIScriptError> errorObject = do_CreateInstance("@mozilla.org/scripterror;1"); ... if (!report && message) { rv = errorObject->Init(msg.get(), nsnull, nsnull, 0, 0, 0, category); } Instead, we should just log the message.
Just logging the message doesn't let you set the category, does it?
(In reply to comment #1) > Just logging the message doesn't let you set the category, does it? Oh. Hm. That could be a problem.
I'm going to replace the assertion I would've added for bug 312630 with a warning. There's just too many instances to justify crashing the program.
Keywords: assertion
Assignee: general → nobody
QA Contact: ian → general
https://bugzilla.mozilla.org/show_bug.cgi?id=1472046 Move all DOM bugs that haven’t been updated in more than 3 years and has no one currently assigned to P5. If you have questions, please contact :mdaly.
Priority: -- → P5
Component: DOM → DOM: Core & HTML

NS_ScriptErrorReporter seems to be gone.

Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.