Re: Setting plugin activation state from addons

On 13 Mar 2014, at 14:37, Marcin Pijanowski <[email protected]> wrote:
> Content of signplugin.js.
> pref("dom.ipc.plugins.enabled.npsignplugining.dll", false);
>  
> and now I want to add pref - plugin.state.<name>
>  
> plugin.state. = 0 ‘never active’
> plugin.state. = 1 ‘always active’
> plugin.state. = 2 ‘default state, does nothing’

The value for plugin.state.yourplugin should be:
* 0 for ‘never activate’ (disable)
* 1 for ‘ask to activate’ (click-to-play)
* 2 for ‘always activate’

The upcoming change sets your plugin state to 1, you want to set it to 2.

> in my case I add
> pref("plugin.state.ING BusinessOnLine", 1);

The name is probably different, here is what you can do to see how this works:
Your plugin should get listed in Tools->Addons->Plugins as ‘ask to activate’. 
There, set it to e.g. ‘always activate’. Now check about:config by filtering for
“plugin.state.”. There should be an entry for your plugin, probably
“plugin.state.npsignplugining”.

> pref("dom.ipc.plugins.enabled.npsignplugining.dll", false);

Please don’t use this pref if at all possible, we really want all plugins to run out-
of-process for stability reasons etc.

> How and where to check whether this solution works correctly?

Verify by installing and checking the plugin activates or looking at the prefs.


Georg