Closed Bug 48299 Opened 25 years ago Closed 24 years ago

need to distinguish between chrome/content in JS console messages

Categories

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

defect

Tracking

()

RESOLVED FIXED

People

(Reporter: mike+mozilla, Assigned: mike+mozilla)

Details

(Whiteboard: [nsbeta3-])

Attachments

(2 files)

Script error reports going thru the JS console have a 'category' field that says something about where the error originated. Currently, the layout error reporter says 'XUL/Content JavaScript', which doesn't distinguish between errors in the UI JS code itself and in downloaded content. This is a useful distinction; users might be confused on seeing errors resulting from XUL js. It'd be good to provide a way to distinguish. Ben, you had console code that used this; any chance of getting it in?
Ben - I remember you had a number of enhancements to the console that never made it in and were partially gated on this bug. Are those still live? Is there a bug for them?
Status: NEW → ASSIGNED
The chrome-error-suppressing side of things wasn't blocking anything else I don't think... the other bug was that I needed to know when a page with an error had been cleared so that I could remove the notification from the statusbar. that was preventing me from implementing statusbar notification of errors.
cool, ok now I'll hook up some kind of check menuitem in the console that lets you selectively enable chrome error notifications...
Nominating nsbeta3. - It's an itty-bitty, local fix. - Users currently have no way of filtering out JS errors from the javascript in our UI, and will be confused by them. - This is needed to solve that. - We will ship with JS errors in our UI. - Confusion results in tech support calls, and costs money!
Keywords: nsbeta3
Sounds like a good idea, but is it your highest priority?
Whiteboard: [nsbeta3-]
r=jst for the last patch
sr=?
sr=jband
Fix checked in.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: