Catch up on stories from the past week (and beyond) at the Slashdot story archive

 



Forgot your password?
typodupeerror
×
Firefox Media Mozilla Security News

Mozilla Testing Click-to-Play Option For Plugin Content 124

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."
This discussion has been archived. No new comments can be posted.

Mozilla Testing Click-to-Play Option For Plugin Content

Comments Filter:
  • by Anonymous Coward on Friday April 13, 2012 @12:43PM (#39675375)

    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?

  • finally (Score:2, Insightful)

    by Anonymous Coward on Friday April 13, 2012 @12:44PM (#39675411)

    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.

  • for javascript? (Score:5, Insightful)

    by sdnoob ( 917382 ) on Friday April 13, 2012 @12:46PM (#39675433)

    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).

  • by tepples ( 727027 ) <tepples.gmail@com> on Friday April 13, 2012 @01:14PM (#39676039) Homepage Journal
    As I wrote in another comment [slashdot.org], 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.
  • Gnash (Score:4, Insightful)

    by buchner.johannes ( 1139593 ) on Friday April 13, 2012 @01:39PM (#39676481) Homepage Journal

    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.

  • yes, please (Score:4, Insightful)

    by Tom ( 822 ) on Friday April 13, 2012 @04:38PM (#39679043) Homepage Journal

    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.

1 + 1 = 3, for large values of 1.

Working...