![]() Make a directory called distribution in the same directory where the Firefox executable is located. The difference will be the directory we place the add-on in. The user can disable or remove the add-on.įor this scenario, we’re back to using the distribution directory. ![]() Scenario 3: Install the add-on when a new profile is created. Setting this value via distribution.ini will not work. To override this, you’ll need to set the preference toDisableScopes to 0 via a config file or by creating a new prefs file in the defaults/preferences directory. IMPORTANT: If you use this mechanism (which used to work pretty well), your add-ons will be disabled by default. Create a directory with the same ID as your add-on and unzip it into that directory. To include an add-on this way, you need to put it in the extensions directory where the Firefox executable is located. Scenario 2: Include an add-on, prevent users from removing it. They will not be loaded if they are in your add-on. ![]() Also, if your add-on contains search plugins, they have to go in a different directory – distribution/searchplugins/common/. Important Notes: If it is a restartless add-on or an SDK add-on or if the add-on depends on the AddonManager API, this method will NOT work. Then create a directory with the same ID as your add-on and unzip it into that directory. Next create a subdirectory called bundles. To include an add-on in a Firefox distribution and hide it, you need to put it in the distribution/bundles directory. Scenario 1: Include an add-on, prevent users from removing it or disabling it. All of the information I’m about to give applies to all add-ons. This post will detail various ways to do that. One of the questions I get asked a lot is how to integrate a CCK package into a Firefox distribution or install a CCK into an existing Firefox installation.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |