Main Area and Open Discussion > General Software Discussion

Back to Firefox - sudden loud noise

<< < (2/3) > >>

IainB:
Is this the same thing? In Firefox v14 there was a feature introduced for this:

* In the about:config, there is a switch: plugins.click_to_play
* If you set that to True, then you will get no more annoying Autoplay of any plugin.
I started to use it and it seems to have worked faultlessly - I'm up to Firefox v17 now.
There is a similar feature in Chrome, and I use that too.

I think this was the article I originally got the knowledge from:
(Copied below sans embedded hyperlinks/images.)
Firefox 14 to Get Flash Click-to-Play Feature
April 13th, 2012, 12:30 GMT · By Lucian Parfeni

Firefox is on its way to getting a click-to-play feature for plugins, Flash in particular. A similar option is available in Chrome, though it's not enabled by default. The click-to-play option is now available in the latest Firefox Nightly releases, but has to be enabled first.
As you can expect, it's still highly experimental. Google spent more than a year before making the option available to all users by default, but even so it's not enabled by default.
For good reason too, it's a feature best left to more advanced users since it can break sites in non-obvious ways.
The feature works in Firefox pretty much as you'd expect, plugins are not loaded until users click on the Flash element to run it.
"A couple days ago I landed an initial implementation of “click-to-play plugins” in desktop Firefox,"  Mozilla's Jared Wein wrote.
The feature is disabled even in the Nightly builds, you have to navigate to about:config and set "plugins.clik_to_play" to "true."
"When plugins.click_to_play is enabled, plugins will require an extra click to activate and start 'playing' content. This is an incremental step towards securing our users, reducing memory usage, and opening up the web," he explained.
The basic functionality is there and the developer is now working on making the feature run on a per-site basis, enabling users to allow plugins on some sites but on not others.
There's good reason to have plugins blocked by default. For one, if you don't need them, they won't use up memory doing nothing. That's not much of a concern on most desktops, but every bit helps.
Beyond that, blocking plugins removes a big cause of instability, Flash banner ads or heavy Flash sites won't run until you enable them. It also makes it harder to exploit vulnerabilities that creep up in plugins perhaps more so than in any other piece of software.
If all goes smooth, Firefox 14 should be sporting the feature, but even so it will be a while before it's something that most Firefox users will be able to enjoy.

--- End quote ---

MilesAhead:
I started to use it and it seems to have worked faultlessly - I'm up to Firefox v17 now.
There is a similar feature in Chrome, and I use that too.
-IainB (November 08, 2012, 12:34 AM)
--- End quote ---

Thanks. I've set it. Trying it out now. :)

Edit: It does block autoplay.  But it has the side-effect I don't get the mp3 download links. Stop AutoPlay allows me to see the links. I guess it's worth carrying one extra AddOn to avoid installing Opera just for that. :)

I use the Plugins Disabled in chromium too. That works on most sites but has the same mp3 link blocking side-effect. :(

4wd:
For interests sake, in about:config there's also media.autoplay.enabled which acts on HTML5 content.

MilesAhead:
For interests sake, in about:config there's also media.autoplay.enabled which acts on HTML5 content.
-4wd (November 08, 2012, 05:39 PM)
--- End quote ---

Thank you. That seems to fix it up. :)

IainB:
media.autoplay.enabled
-4wd (November 08, 2012, 05:39 PM)
--- End quote ---
That's interesting.
Mine was set to "True" - that's the default state.
That's why I couldn't understand @MilesAhead's earlier difficulty.

Navigation

[0] Message Index

[#] Next page

[*] Previous page