Closed
Bug 275827
Opened 20 years ago
Closed 20 years ago
Javascript Console not enabled by default
Categories
(Toolkit Graveyard :: Error Console, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: pwilson, Assigned: bugs)
Details
The about:config option Javascript.options.ShowInConsole was turned off by default when I installed Firefox. When displaying the Javascript Console my expectation of seeing any JS parsing errors lead me to spend many hours persuing other possible causes. It should be turned on by default. I previously had Mozilla 1.7 installed - is this an artefact of the previous installation?
Comment 1•20 years ago
|
||
Looks to me like showinconsole controls whether or not errors in chrome JavaScript are shown, not whether or not errors in content JavaScript are shown. With it false, data:text/html,<script>foo=</script> still shows up as an error in the console. Is it your contention that people who will be helped by seeing ""Access to XPConnect service denied. [nsILDAPMessageListener::onLDAPMessage]" nsresult: "0x8057001e (NS_ERROR_XPC_JS_THREW_STRING)"" but can't find the pref in about:config are more numerous than those who will be baffled and alarmed (and will file duplicate bugs) when Page Info messes up its tree and throws a string of thirty errors?
Comment 2•20 years ago
|
||
comment #1 is absolutely correct. The variable in question helps debug chrome javascript and should not be turned on by default
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WONTFIX
Updated•16 years ago
|
Product: Firefox → Toolkit
Updated•8 years ago
|
Product: Toolkit → Toolkit Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•