InformAction Forums

Since the release of 2.3.8RC1 I have enabled the click_to_play experimental feature in about:config. Of course the NoScript preference boolean is untouched but I notice no difference. Is this supposed to be transparent? I think Tom is familiar with my configuration by now considering how privacy-conscious I am so there is no need to mention everything is blocked by default. Opening about:config freezes Firefox for about 120 to 180 seconds I guess because there is so much inside so I am hesitant to open it again but I will if need be. I do not understand the significance of the implementation in NoScript. It seems NoScript already provides this feature so what does it matter if [1] the native implementation is enabled and [2] NoScript integrates with it?

PS. It feels good to be back on here.

Allow me to correct myself. Enabling plugins.click_to_play does make a difference – but for the worst. When I am on a web page with a shockwave-flash object and temporarily allow it in NoScript's context menu the video does not play. I know for a fact it is due to Firefox's preference because I just disabled it and everything works OK now. My assumption was by allowing the shockwave-flash object in NoScript's context menu would also allow it in the other. Something tells me I am wrong and if I am not there is either a bug in NoScript's integration or the experimental Firefox feature itself. Either way it does not work for me.

With a current Nightly (possibly Aurora too?), if you have (FF) plugins.click_to_play enabled, you are prompted before (plugin) media plays.

With NoScript, before 2.8 & with "Apply these restrictions to whitelisted sites too" enabled, you would get a double prompt before a clip would play. Once (first) from NoScript, & then again from FF.

With 2.8, & with "Apply these restrictions to whitelisted sites too" enabled, you only get one prompt, from NoScript, the second prompt from FF is bypassed.

That part seems to make sense.

Though if you toggle noscript.smartClickToPlay (to false), then you only get the FF prompt?
And I would have again expected both prompts - first from NoScript & then from FF, as it worked before NoScript 2.8?

Nightly builds are 14.0; I am using Aurora which had click-to-play included since Aurora 11.0 I think. I know it was included in 12.0. I should have only encountered one prompt from NoScript but still after allowing the object it does not play when Firefox's preference is enabled. That is why I think there is something wrong with either Firefox or NoScript 2.3.8RC1.

I think something happened?

After reverting noscript.smartClickToPlay back to true, nothing is being blocked, not from NoScript nor from FF?

(I've been testing at Youtube.)

I never toggled that preference. Since NoScript blocked plug-ins from running I never saw a reason to enable Firefox's click-to-play function. Now that NoScript has native integration I thought it would be sensible to make use of it. When I turned on Firefox's preference and continued as usual nothing would play. I then turned off the preference [NoScript's noscript.smartclicktoplay is still untouched] everything is as how it was before I upgraded to 2.3.8RC1.

Identities Infinite wrote:Nightly builds are 14.0; I am using Aurora which had click-to-play included since Aurora 11.0 I think. I know it was included in 12.0.

Click-to-play is still experimental and evolving in Nightly (14), therefore it being broken (if even present in any embryonic and non-supported form) in Aurora is definitely expected.

If you really want to experiment with it, please use Nightly.

therube wrote:I think something happened?

After reverting noscript.smartClickToPlay back to true, nothing is being blocked, not from NoScript nor from FF?

(I've been testing at Youtube.)

But are you testing always with the same movie?
If so, did you restart the browser or reset the temporary permissions after allowing the first time?

No, I was using different clips.
Otherwise I would have had to do something to get the placeholders to reappear.

(I was getting a bit confused, & not in a position to look further at the moment. BTW, I was using FF Nightly in my testing.)

With today's Nightly, I'm not able to duplicate my issues from the other day.
All looks to be working as expected.

Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120418 Firefox/14.0a1 SeaMonkey/2.11a1

I just updated to the new Aurora today. I enabled the native plug-in preference and tried again but the same thing happened: nothing played when the object was temporarily allowed. Did the feature not get fixed before Aurora 14 was released?