Slashdot Mirror

← Back to Stories (view on slashdot.org)

Firefox 28 Arrives With VP9 Video Decoding, HTML5 Volume Controls

Posted by Soulskill on from the onward-and-upward dept.

An anonymous reader writes "Mozilla today officially launched Firefox 28 for Windows, Mac, Linux, and Android. Additions include VP9 video decoding, Web notifications on OS X, and volume controls for HTML5 video and audio. Firefox 28 has been released over on Firefox.com and all existing users should be able to upgrade to it automatically. The full release notes are available. As always, the Android version is trickling out slowly on Google Play (Android release notes)." Mozilla also announced tools to bring the Unity game engine to WebGL and asm.js.

5 of 142 comments (clear)

  1. Automatically? by agm · · Score: 3, Informative

    ...and all existing users should be able to upgrade to it automatically

    Not for those of us running Gentoo linux.

  2. Re:VP9 by DMUTPeregrine · · Score: 3, Informative

    You have to enable HTML5. https://www.youtube.com/html5

    --
    Not a sentence!
  3. Re:VP9 by Lennie · · Score: 4, Informative

    Have you tried enabling it ?:

    http://youtube.com/html5

    It has been improving, but only very slowly.

    --
    New things are always on the horizon
  4. Re:Now is the time to turn automatic updates off by Dagger2 · · Score: 3, Informative

    As covered on Slashdot previously: Australis is landing. If you read the official blog post you'll get the impression that this is all about improvements, but if you pay a bit more attention you'll see it's actually more about removing most of the in-browser customizability.

    That's such a big change in direction that I don't think it's reasonable to consider Firefox 29 the same browser as previous versions, and I don't think anybody should automatically move from one to the other.

  5. Re:I'm still alive by Anonymous Coward · · Score: 5, Informative

    Are you on Windows 7 with IE 10 installed and broken R600 graphics drivers?

    FTFO.

    It boggles my mind that they released the browser with this bug unresolved.

    You can only resolve bugs in your code. That's a bug in ATI's drivers, what they can do is to work around the bug, which they did.