Click-to-play plugin blocks coming in Firefox 17

Firefox 17, coming out today on Beta, introduces a new solution for dealing with vulnerable or outdated plugins. Plugins that are blocked with the click-to-play flag will not load by default, but can be easily activated by users. This gives us a more user-friendly way to warn about plugins that should be updated, that give users better control over their browsing experience.

The large scale plugin update notification we deployed last week used the old update notification mechanism for Firefox 16 and below, and the new click-to-play mechanism for Firefox 17 and above. If you have old versions of Flash, Adobe Reader or Silverlight and you’re on 17, you will see the click-to-play block next time you visit a page that uses one of these plugins.

This is a real problem at companies that have administrator locked down… the end users cannot update plugins like Shockwave. I’m finding problems with it, where clicking to let it run doesn’t work. (Nightly 19.0a1 (2012-11-01) )

@Jorge: Flashblock may give a similar user experience to click-to-play, but it’s not reliable; pages have ways to work around it. You should not rely on FlashBlock for security purposes.

Plus, it only applies to Flash.

A better solution is to use the NoScript addon. Enable Options-Embeddings-‘Apply these restrictions to whitelisted sites too’, and then select ‘Scripts Globally Allowed’. You get reliable click-to-play for every kind of plugin – or a configurable subset of them – plus the ability to forbid JavaScript on demand for sites you don’t trust, plus filters for attacks like cross-site scripting and clickjacking. And it integrates with the built-in click-to-play feature, so when you tell NoScript to allow an object, it automatically tells Firefox to allow it.

With all these updates, my Firefox is becoming less and less stable with each improvement. The only advancement I see that Really works for me is the option to reopen existing windows before the crash.

When we were at low single digit versions, I could have open dozens of windows for Weeks with No Problem at all, all the pages I frequent I could keep open and and refresh regularly. and ALL the Captchas worked fine – it was heaven. Now with each upgrade it is a mess, I’m leery about upgrading anymore. I’m lucky if I can have open more then 4 windows for a few hours before it locks up and crashes, this is a daily occurrence, god help me if try to get I-Heart radio working, it WILL lock up in minutes. I tried uninstall and reinstall and all that BS, Nothing works.

Is there there someplace I can go to get the older versions? and forget the updates.

I updated to the lastest version of Adobe Flash in ‘Firefox 17’. Verified by Adobe installed and running.
I re-started browser, but the latest version for Windows XP is still showing up as outdated when I run the Firefox addons check? This has never happened before.

I uninstalled and re-installed the latest version, but am still getting the update addon message for Adobe Flashplayer? How can this be fixed?

After posting this issue, I ran addons check again, and Flashplayer showing updated? But now it shows my Java addons need to be updated. However, when I check Java, I’m already currently using the latest installed Java 7.9 for Windows XP? Why is it showing I need to update it? Do I need to uninstall and re-install the same version?

Add me to this dysfunctional ff family with Ameritrade. It hangs on connecting to dealply for about a minute through the first layer of security and halts completely on the 2nd layer. Someone needs to go back & try again. Switching to chrome so google can track my ever move. Just what I wanted. I’ll check back in a few months to see if it’s been fixed.

I’ve installed the latest version of FireFox & the Click-to-Play add in…but when I went to test it, it’s not blocking Flash videos…nor am I seeing the “lego” looking icon to the left of the address bar. This works at my office…but we’re all running Windows 7. The other office that we’re having problems with is running XP. Could that be why? I checked in about:config & it’s enabled. I’m just not sure where else to check.

If the about:config preference is set, it should work. However, if that machine is running XP, it might also be running an old version of Firefox. Maybe it’s running a version that doesn’t support click-to-play?