Closed Bug 1263186 Opened 4 years ago Closed 4 years ago

Devtools preference devtools.errorconsole.enabled missing in Seamonkey

Categories

(SeaMonkey :: General, defect, minor)

defect
Not set
minor

Tracking

(seamonkey2.46 fixed)

RESOLVED FIXED
seamonkey2.45
Tracking Status
seamonkey2.46 --- fixed

People

(Reporter: frg, Assigned: frg)

References

Details

Attachments

(1 file)

Using latest trunk I get the folling error in the web console:

>> Timestamp: 4/8/2016 5:14:24 PM
>> Error: NS_ERROR_UNEXPECTED: Component returned failure code: 
>> 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch.getBoolPref]
>> Source File: chrome://navigator/content/webDeveloperOverlay.js
>> Line: 206

The preference does not exist in Sea Monkey.

VS2015 x64 en-US build
>> User agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:48.0) 
>> Gecko/20100101 Firefox/48.0 SeaMonkey/2.45a1
>> Build identifier: 20160408154200
Summary: Devtools preference devtools.errorconsole.enabled missing → Devtools preference devtools.errorconsole.enabled missing in Seamonkey
Remove this:

    // Enable Error Console?
    var consoleEnabled = Services.prefs.getBoolPref("devtools.errorconsole.enabled");
    toggleCmd("Tools:ErrorConsole", consoleEnabled);

Also remove this:

    <command id="Tools:ErrorConsole" oncommand="toJavaScriptConsole()" disabled="true" hidden="true"/>
The patch. Tested and seems to work.
Attachment #8739470 - Flags: review?(philip.chee)
Assignee: nobody → frgrahl
Status: NEW → ASSIGNED
Attachment #8739470 - Flags: review?(philip.chee) → review+
Depends on: 1258985
http://hg.mozilla.org/comm-central/rev/abc74bba07dc
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → seamonkey2.45
What kind of Error console is this? Have they removed it from Firefox?
(In reply to :aceman from comment #4)
> What kind of Error console is this? Have they removed it from Firefox?
This is the traditional toolkit Error Console. Bug 1258985 just removes the menu item from the Firefox Devtools UI. The Error Console itself is not affected. This should not affect Thunderbird since you aren't exposing the Devtools Client UI anyway.
Thanks. So the console backend is still in Toolkit in for now and as we expose a link to it in the UI (tools->error console) it still works.
You need to log in before you can comment on or make changes to this bug.