/./toolkit/components/exthelper/extApplication.js in your copy of fuelApplication.js as needed copy files fuelApplication.js and fuelApplication.manifest from browser/fuel/src for instance into your components/ directory.If your application is based on Gecko 2.0, you need to register a component through the new component registration because the extension manager uses FUEL, namely Application.restart(), to restart your xulrunner-based application after any change (installation, removal, enabling, disabling) in the extensions' list: Pref("extensions.getMoreThemesURL", "chrome://mozapps/locale/extensions/extensions.properties") Pref("extensions.getMoreExtensionsURL", "chrome://mozapps/locale/extensions/extensions.properties") Pref("", "chrome://mozapps/locale/extensions/extensions.properties") Pref("extensions.ignoreMTimeChanges", false) Pref(".chrome", "Extension:Manager-extensions") Pref(".skin", "Extension:Manager-themes") Pref("", "chrome://mozapps/content/extensions/extensions.xul?type=extensions") Pref("", "chrome://mozapps/content/extensions/extensions.xul?type=themes") The following prefs must also be set to make the XPInstall dialog, extension manager, and theme manager work: pref("", "chrome://mozapps/content/xpinstall/xpinstallConfirm.xul") However, it seems that with XULRunner 1.9 the XULRunner directory is ignored, while the profile and application directories are checked. XULRunner 1.8.0 does not load extensions from the application directory only the XULRunner directory and the user profile directory are checked.
#Firefox developer edition enable xpinstall install
To be able to install any extensions, you first need to enable the Extension Manager in application.ini. Contains tons of non-working code (bit rot).
0 kommentar(er)
