Slashdot Mirror


Firefox 26 Arrives With Click-To-Play For Java Plugins

An anonymous reader writes "Mozilla today officially launched Firefox 26 for Windows, Mac, Linux, and Android. Additions include Click-to-Play turned on by default for all Java plugins, more seamless updates on Windows, and a new Home design for Android. Firefox 26 has been released over on Firefox.com and all existing users should be able to upgrade to it automatically. As always, the Android version is trickling out slowly on Google Play. Release notes are here: desktop and mobile."

4 of 208 comments (clear)

  1. great... by lyapunov · · Score: 4, Informative

    In the mean time they have made it substantially more difficult to configure the rejection of cookies.

    Jesus... I'm actually thinking IE is better at this point.

    --

    Either give it away or get top dollar, but never sell yourself cheap.
    1. Re:great... by DMUTPeregrine · · Score: 5, Informative

      Try the self-destructing cookies addon.
      When you close a tab, the cookies created by that tab are removed. You can whitelist domains to prevent their cookies from being deleted.
      This way, sites see cookies as being enabled, but can't track you after you close the tab.
      https://addons.mozilla.org/en-US/firefox/addon/self-destructing-cookies/

      --
      Not a sentence!
  2. Re:A good start.. by bsmedberg · · Score: 4, Informative

    We studied doing this for Flash as well. Check out the user research study. We determined that the vast majority of users would merely be annoyed by making Flash click-to-play, and we wouldn't actually be improving security or performance for most users.

    As noted in other comments here, you can mark Flash as click-to-activate yourself in the Firefox addons manager, or get more fine-grained control over which Flash actually runs by installing an addon like Adblock.

    Our long-term strategy is to make it so that nobody needs to use plugins by adding new web APIs; to reimplement content like PDF and Flash in JS so that we can have control over the performance; and to use the mobile web as leverage to get new sites to use native HTML APIs like <video> to wean the world off of plugins.

  3. Re:Unintended consequences by hairyfeet · · Score: 4, Informative

    But whose fault is that? Put the blame where it lies, Steve jobs trying to push his appstore crapstore lock in. I have flash on my fricking THREE YEAR OLD single core cellphone and ya know what? plays great. try HTML V5 with H.264 on anything less than a dual core and see what you get,even with hardware acceleration its a fricking pig.

    So call a spade a spade, the killing of flash on mobile didn't have a damned thing to do with compatibility, or battery life, it had to do with Steve jobs making damned sure you weren't getting shit on that iPad without giving him 30%.

    --
    ACs don't waste your time replying, your posts are never seen by me.