627045 - An error is informed when open Extensions Manager in a Xul app

Status: RESOLVED INVALID

(Core :: General, defect)

Description

[brito.pro]

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Ubuntu/10.04 Chromium/8.0.552.224 Chrome/8.0.552.224 Safari/534.10
Build Identifier: Xulrunner 1.9.2.13

Doing something like:

app = "chrome://mozapps/content/extensions/extensions.xul";
window.open(app,'Test','chrome, width=640, height=480').moveTo(0,0);

in my javascript, opens the extensions manager sucessfully, but the following message is shown in the jsconsole:

Error: uncaught exception: [Exception... "Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch2.getBoolPref]" nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)" location: "JS frame :: chrome://mozapps/content/extensions/extensions.js :: updateGlobalCommands :: line 2388" data: no]

My app and the Extensions Manager are working fine, but I'm worried about this error message.

Reproducible: Always

Steps to Reproduce:
Open the extensions manager from javascript code, like:

app = "chrome://mozapps/content/extensions/extensions.xul";
window.open(app,'Test','chrome, width=640, height=480').moveTo(0,0);
Actual Results:  
The error message is shown:

Error: uncaught exception: [Exception... "Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch2.getBoolPref]" nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)" location: "JS frame :: chrome://mozapps/content/extensions/extensions.js :: updateGlobalCommands :: line 2388" data: no]

Expected Results:  
No errors should happen.

Comment 1

[brito.pro]

Answered: http://stackoverflow.com/questions/3987374/error-when-opening-the-extensions-manager-from-xul-app/4768282#4768282

"Lines 2387-2388 of extensions.js are:

if (!gInstalling &&
    (gPendingActions || gPref.getBoolPref(PREF_EXTENSIONS_DSS_SWITCHPENDING)))
So I guess that your application doesn't have the extensions.dss.switchPending preference set. For some reason this doesn't live in all.js so you have to set it to false in your application's default preferences."