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)
Core
DOM: Core & HTML
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?
Assignee | ||
Comment 1•25 years ago
|
||
Assignee | ||
Comment 2•25 years ago
|
||
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
Comment 3•25 years ago
|
||
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.
Comment 4•25 years ago
|
||
cool, ok now I'll hook up some kind of check menuitem in the console that lets
you selectively enable chrome error notifications...
Assignee | ||
Comment 5•25 years ago
|
||
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
Comment 6•25 years ago
|
||
Sounds like a good idea, but is it your highest priority?
Whiteboard: [nsbeta3-]
Assignee | ||
Comment 7•24 years ago
|
||
Comment 8•24 years ago
|
||
r=jst for the last patch
Assignee | ||
Comment 9•24 years ago
|
||
sr=?
Comment 10•24 years ago
|
||
sr=jband
Assignee | ||
Comment 11•24 years ago
|
||
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.
Description
•