Slashdot Mirror


Firefox 51 Arrives With HTTP Warning, WebGL 2 and FLAC Support (venturebeat.com)

Reader Krystalo writes: Mozilla today launched Firefox 51 for Windows, Mac, Linux, and Android. The new version includes a new warning for websites which collect passwords but don't use HTTPS, WebGL 2 support for better 3D graphics, and FLAC (Free Lossless Audio Codec) playback. Mozilla doesn't break out the exact numbers for Firefox, though the company does say "half a billion people around the world" use the browser. In other words, it's a major platform that web developers target -- even in a world increasingly dominated by mobile apps.

4 of 130 comments (clear)

  1. Does it have separate processes for each tab? by Master5000 · · Score: 2, Insightful

    Yet? I'll give it a chance when it's at least as sandboxed as chrome.

  2. Firefox aka "the java applet browser" by IGnatius+T+Foobar · · Score: 4, Insightful

    Although the world has largely switched to Chrome, the remaining use for Firefox is as the one browser that is still willing to support Java applets. Lots of people who work in IT have a VM or a jumpbox whose only purpose is to run Java applets inside of Firefox (for example, to do maintenance on some piece of equipment with a Java-applet-based configuration tool -- I'm talking to you, EMC) -- and *never* *run* *updates* because changing the browser or java version even slightly will break the whole thing.

    --
    Tired of FB/Google censorship? Visit UNCENSORED!
  3. Re:Warning for websites collecting passwords? by Thud457 · · Score: 3, Insightful

    Not relevant to the HTTP/S issue, but not too long ago, the UK was spoofing slashdot to attack their targets, so it could happen.

    --

    the preceding comment is my own and in no way reflects the opinion of the Joint Chiefs of Staff

  4. Is there any way to tell? by Torodung · · Score: 4, Insightful

    Is there any way to tell which extensions are blocking multiprocess? My about:support page says multiprocess is disabled because of extensions, but it doesn't say which ones. It seems like they should publish this information, perhaps in a field on AMO. A Google only turns up results for developer testing or small lists, it says nothing about a complete list of incompatible extensions.

    I don't know if anyone at Mozilla reads Slashdot any longer, but I think this would be a worthwhile documentation project that would help users demand extension authors make their software compatible, thus aiding the roll-out.