1289580 - plugins.click_to_play=false does not work

Status: RESOLVED WONTFIX

(Core Graveyard :: Plug-ins, defect)

Description

[Brian Peppers]

Attachment: plugins.click_to_play 1.png

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:47.0) Gecko/20100101 Firefox/47.0
Build ID: 20160623154057

Steps to reproduce:

Using the latest version of Firefox and the latest version of Microsoft Silverlight, (flash is not installed), setting plugins.click_to_play=false in about:config does not make "click to play" stop doing its thing.  Setting plugins.click_to_play to true has the exact same result.


Actual results:

I went to the site I use: https://jet.asmnet.com/
This site runs on Microsoft Silverlight®
This was set in about:config ... plugins.click_to_play=false
But Click to Play still came on.

I have two screenshots.  I will see if I can upload both.  But it does not look like I can upload more than one so I put them on imgur.
http://i.imgur.com/GIIXjlq.png
http://i.imgur.com/JHVWxF8.png



Expected results:

Setting plugins.click_to_play=false should have actually, actually, actually disabled "click to play".

Comment 1

[Brian Peppers]

I forgot to mention, Silverlight is set in the "Addons Manager" to "Always activate".  And "ask to activate" is grayed out oddly so it cannot be selected, maybe because I have the latest version of Silverlight.

Comment 2

[Loic]

WFM with FF47

Could you test with a fresh profile, please.
https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles

Comment 3

[Loic]

Remember FF 64 bits will not support 64 bits plugins, only Flash is supported.

Comment 4

[Brian Peppers]

I tried again after making a fresh profile and the same thing happens.
http://i.imgur.com/7REvhut.png
http://i.imgur.com/mo1JMjS.png
The setting in about:config of plugins.click_to_play has absolutely no effect whether set to true or false. "Click to play" is always on no matter what.



For, "Remember FF 64 bits will not support 64 bits plugins, only Flash is supported." I cannot find whether my Firefox is 32 or 64 bits, only that it is version 47.0.1.  Silverlight runs just fine.  Also Microsoft will only let me download one type of Silverlight, not 32 or 64 bit, just whatever is on Microsoft's website.

The problem is not whether any extentions are compatible.  The problem is that Firefox recent versions do not use plugins.click_to_play and ignore the value set for it.

Comment 5

[Brian Peppers]

Hi.  So low-orbit-ion-cannon mentioned 64 bit Firefox.  So after a lot of hunting, I found where Mozilla hid their full 32 bit version of the latest Firefox and not the really annoying installer--I hate those installer things that have to download a large amount of stuff first.  So I have installed a second version of Firefox, a 32 bit version.

Both versions use my same profiles and are nearly identical.  I just have to completely close one before the other will run as Firefox won't run both at once.

So anyway, in the 32 bit version of Firefox, the exact same thing happens as in the 64 bit Firefox.  That is, Firefox ignores the value of plugins.click_to_play and always acts like it's true even when it's set to false.

Comment 6

[Masatoshi Kimura [:emk]]

plugins.click_to_play=false no longer has an effect. The corresponding new pref setting is plugin.default.state=2.

(In reply to Loic from comment #3)
> Remember FF 64 bits will not support 64 bits plugins, only Flash is
> supported.

Actually Firefox Win64 supports Silverlight (bug 1225293).

Comment 7

[Brian Peppers]

Setting
plugin.default.state=2
completely works in both 32 and 64 bit versions of Firefox.  The only thing now is to update the help pages at Mozilla.  I searched Google for plugin.default.state and got a few bits on forums and bug report chat with contradictory information on what values 0, 1, and 2 do for plugin.default.state

But plugin.default.state = 2 disables autoplay correctly so I can have NoScript handle it.

Comment 8

[Benjamin Smedberg]

plugins.click_to_play does not have any effect (intentionally). As described, the per-plugin states are now used, and controllable using the addon manager UI. I'm going to resolve this WONTFIX.

Comment 9

[Brian Peppers]

Is there a way to disable that harassing popup permanently for everything?