Slashdot Mirror


Mozilla Plans To Build Virtual Reality APIs Into Firefox By the End of 2015

An anonymous reader writes: Mozilla's VR research team is hard at work making virtual reality native to the web. The group wants more than a few experimental VR-only websites, they want responsive VR websites that can adapt seamlessly between VR and non-VR, from mobile to desktop, built with HTML and CSS . Experimental work is already underway, and now the team says that they 'aim to have support for the WebVR API shipping with our release channel builds of Firefox Desktop by end of this year.' Those with the Oculus Rift developer kit can already try out a few native WebVR experiences using Firefox Nightly.

4 of 91 comments (clear)

  1. Return of VRML? by Frobnicator · · Score: 5, Insightful

    Reading the article, it looks very much like the promises of VRML back in 1994.

    --
    //TODO: Think of witty sig statement
  2. And the Firefox bloat continues to swell by QuietLagoon · · Score: 5, Insightful
    The Firefox market share continues to drop as Mozilla continues to add bloat to what once was an excellent browser.

    .
    One would think that Mozilla would take a step back and think, what might we be doing wrong?.

    But no. Mozilla, instead, accelerates the rate of bloating.

  3. Meanwhile, Firefox 38.0.5 included even more bloat by NotInHere · · Score: 5, Insightful

    The recent release of firefox 38.0.5 on june 2 has been below the radar of many news sites, including Slashdot, because it was only a "patch" release.

    However, 38.0.5 included real feature changes, meaning the inclusion of a proprietary web service. I not just hate that firefox added a proprietary web service prominently to its browser, also they smuggled this in in a patch release, avoiding press attention.

    Firefox isn't a randy bitch dog that every dog inside the SV startup neighbourhood springs on, its a major web browser which respects its users. At least it was until 38.0.5.

    I accepted that they added the social API, I understood their EME changes, I've thought firefox hello was a good addition. But for 38.0.5 pocket integration, I'm heavily disappointed by mozilla.

  4. But what do the users want? by ShaunC · · Score: 3, Insightful

    Mozilla's VR research team is hard at work making virtual reality native to the web. The group wants more than a few experimental VR-only websites, they want responsive VR websites that can adapt seamlessly between VR and non-VR, from mobile to desktop, built with HTML and CSS .

    I'm not really concerned with what Mozilla's VR research team wants, I want to know why Mozilla doesn't care what their users want. I want to know why the slick, responsive, optionally extensible browser with a low memory footprint that millions of people switched to because it was a slick, responsive, optionally extensible browser with a low memory footprint has turned into a bloated behemoth that now includes such essentials as a built-in video chat client. The list of things I have to manually disable on a fresh Firefox install is bordering on inexcusable these days. Just filtering on about:config for enabled, there are 24 options I've changed from their defaults.

    If I wanted Firefox to be my fucking operating system, I would buy a device that runs Firefox OS. I don't, and I haven't. I, as a user, want a browser.

    Mozilla's continued race to become Chrome makes me question more and more with each Firefox update why I don't just give in and run Chrome itself. At this point I really have to wonder if the Firefox project isn't being intentionally torpedoed by some Google plants on Mozilla's payroll. There seem to be few explanations left.

    --
    Thanks to the War on Drugs, it's easier to buy meth than it is to buy cold medicine!