Closed
Bug 125181
Opened 23 years ago
Closed 23 years ago
Add pref to filter chrome:// errors in JS Console
Categories
(Core Graveyard :: Error Console, defect)
Core Graveyard
Error Console
Tracking
(Not tracked)
VERIFIED
FIXED
mozilla1.0
People
(Reporter: bc, Assigned: bugzilla)
Details
Attachments
(2 files)
4.71 KB,
patch
|
bugs
:
review+
hewitt
:
superreview+
|
Details | Diff | Splinter Review |
15.00 KB,
patch
|
Details | Diff | Splinter Review |
Internal JavaScript errors are reported to the JS Console using urls of the form chrome://xxx, e.g. Error: redeclaration of const hide Source File: chrome://wallet/content/walletOverlay.js Line: 1 These errors can be filtered in the JS Console based upon the chrome:// protocol. These errors are useful for Mozilla developers to find and correct JavaScript errors however they are not useful for Web Developers who are not concerned with the internals of Mozilla. These internal errors in the JS console are an embarrassment when attempting to teach Web Developers how to use the JS Console to debug their JavaScript. Of course the best solution would be to not have internal JS errors at all, but that is not likely. There would not necessarily need to be a UI for this pref.
Assignee | ||
Comment 2•23 years ago
|
||
I would prefer to see us not do any work at all to report our errors if it's a release build, rather than filtering out at the last possible moment. But I wonder if this info is useful for tech support, in which case having a way to turn them on would be useful.
![]() |
||
Comment 3•23 years ago
|
||
These errors are incredibly helpful in nightlys if nothing else.... Having a way for bug reporters to be able to provide that information would be good.
Assignee | ||
Comment 4•23 years ago
|
||
Oh, definitely. We should probably have them on in milestones, too. We should provide an easy way for distributors to turn them off, though.
Comment 5•23 years ago
|
||
Hiding the bugs under the carpet won't make them go away. I would find it more embarrassing to hide them than to have them to begin with. Oh yeah, and not being able to hide them is an extra incentive to fix ;-)
Reporter | ||
Comment 6•23 years ago
|
||
What is embarrassing is trying to teach someone to use the JavaScript Console to determine why their web page is not being displayed properly and have to teach them to ignore the multitude of internal errors to find the relevant errors for their web page. This is not intended to sweep anything under the rug, but is intended to make supporting commercial releases of the browser easier. Of course these bugs should be fixed, and I heartily invite any and all to do just that. But I get enough denigrating comments from users without having to deal with this cruft that no one else seems to care about. I *need* a simple and clear mechanism to communicate errors in JavaScript to end users and web developers who do not want to debug Mozilla.
Comment 7•23 years ago
|
||
I couldn't agree more with Bob.
Comment 9•23 years ago
|
||
Mass move of nsbeta1+ bugs that didn't have a valid MachV milestone to mozilla1.0.
Target Milestone: --- → mozilla1.0
Assignee | ||
Comment 11•23 years ago
|
||
Comment 12•23 years ago
|
||
Comment on attachment 71244 [details] [diff] [review] patch sr=hewitt
Attachment #71244 -
Flags: superreview+
Comment 13•23 years ago
|
||
Comment on attachment 71244 [details] [diff] [review] patch r=ben@netscape.com with the 'from chrome' (or similar) text change we discussed on IRC.
Attachment #71244 -
Flags: review+
Comment 14•23 years ago
|
||
a=asa (on behalf of drivers) for checkin to 0.9.9
Assignee | ||
Comment 15•23 years ago
|
||
Fixed.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Comment 16•23 years ago
|
||
small bug. JavaScript is not spelled "Javascript". It "JavaScript". With capital S
Comment 17•23 years ago
|
||
The patch does 3 things: 1. Fixes "JavaScript" spelling in pref-debug.dtd Tested by visually observing debug pane. 2. Renames debugStrictJavascript.label and debugConsoleJavascript.label to debugStrictJavaScript.label and debugConsoleJavaScript.label inside pref-debug.dtd and pref-debug.xul Tested by visually observing debug pane as well as searching LXR for any files that refer to debugStrictJavascript.label 3. Cleans out 434 trailing whitespaces inside pref-debug.xul and consoleBindings.xml Tested by reviewing the lines that patch modifies. As well as visually checking every pref Category with the cleaned files. And checking JS Console during it. (Yes I have no life)
Comment 18•23 years ago
|
||
reopening, review please
Assignee | ||
Comment 19•23 years ago
|
||
Please file a new bug for nits...thanks. The capitalized S does not need to be fixed. This is debug UI!!
Status: REOPENED → RESOLVED
Closed: 23 years ago → 23 years ago
Resolution: --- → FIXED
Updated•16 years ago
|
Product: Core → SeaMonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•