Re: Setting plugin activation state from addons

We decided to automatically activate plugins that are located in extensions.
This change (bug 982101) will land together with making most plugins click-to-play
by default and the whitelist (bug 992995).
That means that plugins bundled in extensions are not affected by the changes.

Note: This is currently targeted for Firefox 30.

Georg

https://bugzilla.mozilla.org/show_bug.cgi?id=982101
https://bugzilla.mozilla.org/show_bug.cgi?id=992995

On 13 Mar 2014, at 21:24, Georg Fritzsche <[email protected]> wrote:

> You can verify this like so:
> * use a new profile in Aurora or Nightly
> * install the old add-on version that doesn’t have the pref
> * check that your plugin is click-to-play on sites that use it (without allowing it there)
> * install your add-on
> * check that your plugin is now always active on the sites
> 
> 
> Georg
> 
> On 13 Mar 2014, at 15:33, Marcin Pijanowski <[email protected]> wrote:
> 
>> I changed to 2.
>> Now I have only one pref in signplugin.js.
>> pref("plugin.state.npsignplugining", 2);
>>  
>> Attachment includes screenshot after installation plugin. In the attachment is also xpi file. Can you install and check it?
>> now is it ok, if not please correct?
>>  
>> --
>> Marcin
>>  
>> From: Georg Fritzsche [mailto:[email protected]] 
>> Sent: Thursday, March 13, 2014 2:56 PM
>> To: Marcin Pijanowski
>> Cc: [email protected]
>> Subject: 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
>> <activePlugin.zip>
>