Closed Bug 989948 Opened 8 years ago Closed 8 years ago

Add-on Debugger: Chrome pref has no default

Categories

(DevTools :: General, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED FIXED
Firefox 31

People

(Reporter: philip.chee, Assigned: jsantell)

References

Details

Attachments

(1 file)

+++ This bug was initially created as a clone of Bug #911098 +++

Mon Mar 31 2014 19:12:51
Error: NS_ERROR_UNEXPECTED: Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch.getBoolPref]
Source file: chrome://mozapps/content/extensions/extensions.js
Line: 995

Mon Mar 31 2014 19:11:55
Error: NS_ERROR_UNEXPECTED: Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch.getBoolPref]
Source file: chrome://mozapps/content/extensions/extensions.xml
Line: 1341

http://mxr.mozilla.org/mozilla-central/search?string=PREF_ADDON_DEBUGGING_ENABLED

This pref "devtools.chrome.enabled" has no default anywhere.
It has default for Firefox[1], but not toolkit, so I guess it needs to move.

[1]: http://dxr.mozilla.org/mozilla-central/source/browser/app/profile/firefox.js#1212
Summary: Implement the UI part of the Add-on Debugger → Add-on Debugger: Chrome pref has no default
Where are we using it from a non-Firefox app?
(In reply to Dave Townsend (:Mossop) from comment #2)
> Where are we using it from a non-Firefox app?

Oh. never mind I see. Yeah either that or just ignore the missing pref in extensions.js
Assignee: nobody → jsantell
Attachment #8399543 - Flags: review?(dtownsend+bugmail) → review+
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Please don't resolve bugs until they land on m-c.
Target Milestone: --- → Firefox 31
QA Whiteboard: [qa-]
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.