Mozilla Testing Click-to-Play Option For Plugin Content
Trailrunner7 writes "Mozilla is developing a feature in Firefox that would require some user interaction in order for Flash ads, Java scripts and other content that uses plugins to play. In addition to easing system slowdowns, the opt-in for Web plugins is expected to reduce threats posed by exploiting security vulnerabilities in plugins, including zero-day attacks. 'Whether you hate them or love them, content accessed through plugins is still a sizable chunk of the web. So much so, that over 99% of internet users have Flash installed on their browser,' writes Mozilla's Jared Wein, the lead software engineer on the project, in a blog post."
Seriously, this is a no-brainer, that has been implemented by tonnes of extensions. So now that we're at version 4000, why is it suddenly a good idea to implement it?
This should have been the default 10 years ago.
I'm a fan of Java, but I still cringe when I go to a web page and the Java console opens.
really? you'd get carpel tunnel if you had to click-to-run every script on most commercial sites these days.
no script is more effective but with a learning curve.
but either method will still have the masses turning the 'feature' off (essentially white-listing everything).
FlashBlock, too.
i would rather see HTML-5 make plugins like flash obsolete
So would I. But first, someone must fix these problems:
i think you need to change the defaults for that. Might be a reason, why some noscript users still use flashblock.
I run ClickToPlugin in Safari for all the reasons above. During general browsing my fan no longer turns on and my battery lasts days.
you need to test scripted svg.
Result of same benchmark with SVG: eight times slower than Canvas.
As I wrote in another comment, both Firefox's implementation of Canvas and Firefox's implementation of SVG are substantially slower than Flash Player at playing back vector animations. Furthermore, most web browsers don't provide an API for a JavaScript program to (ask the user's permission to) turn on the camera and microphone. Once Firefox's implementation of Canvas becomes competitive in frame rate and once a device API becomes widely implemented, I will become more inclined to agree with you. Until then, SWF is the only way to push certain features out to users of IE 8 who lack permission to install other browsers (e.g. work break room, public library) because Adobe Flash Player is far more widely installed than Google Chrome Frame.
I've tried this on numerous occasions, the more advanced users eventually click 'Allow Scripts Globally", the less advanced keep calling me until I click 'Allow Scripts Globally".
I personally love it, easy-peasy black/white-list. My other apps do not stutter and bog whenever I scroll a page or open a new one. Pages load faster or not at all(both good IMO). Google's auto-search doesn't clog up my 1MB connection or freeze FF trying to force feed me their assumptions(must remove Goog from pre-loaded whitelist). Minimal ad tracking tools/cookies/malware collecting in my system, bleachbit completes in record time. My whitelist allows mo-add-ons page, my local library and some local devices. I'm typing now with /. & FSDN blocked. With the exception of moderation, the site suits me better with them blocked!
Imagination drew in bold strokes, instantly serving hopes and fears, while knowledge advanced by slow increments...
I would like it if one could decide on a per-site basis to play the Flash with Gnash or with Adobe Flash.
Gnash is much faster, plays nicer with the graphic card, and is more secure. I had success using it on several websites.
However it doesn't support many of the newer Flash features, so everyone trying it out will turn away from it.
If there was a "SafeFlash" extension, that would, like HTTPSEverywhere, use Gnash where the website is compatible, a smooth transition away from Adobe Flash (which will be phased out for Linux anyway apparently) would be possible.
NB: The message above might reflect my opinion right now, but not necessarily tomorrow or next year.
Or the users will just move to the browser that doesn't break things since they won't want breakage.
Yeah, It'd require some consensus between Mozilla, Google and Microsoft although the first two would probably be able to force the issue on their own. Note that Apple's already there with iOS. The future is smartphones and tablets and they're already plugin-free, we just need the desktop to catch up.
If all else fails, immortality can always be assured by spectacular error.
On anything that is video (animated images count) or audio, I absolutely want confirmation.
I regularily open several tabs in the background, e.g. go through a news site, open all interesting articles in their own tabs, continue until end of summary page, then go read all of them. The next time some audio suddenly starts blasting through my speakers, drowning out my music, and I have to hunt down the fucking window that does it, I'll do berserk.
Seriously, audio in webpages should always require an explicit user start.
Assorted stuff I do sometimes: Lemuria.org
OK, I don't use Firefox, I use Chrome. And I have plug-ins disabled by default, so they all show up as grey boxes. If I want to run one I right click and select Run. How is this any different?