Slashdot Mirror

← Back to Stories (view on slashdot.org)

Firefox 4 Web Demos: Web O' Wonder

Posted by timothy on from the glad-the-browser-wars-continue dept.

An anonymous reader writes "Similarly to Google with Chrome Experiments and Microsoft with Internet Explorer Test Drive, Mozilla has developed an HTML5 demo site to showcase the latest features supported by Firefox 4. Mozilla's Paul Roget writes, 'Firefox 4 is almost here, and comes with a huge list of awesome features for web developers. In order to illustrate all these new technical features, we put together several Web demos. You'll see a couple of demos released every week until the final version of Firefox 4. You can see the first 3 demos online now on our brand new demo web site: Web O' Wonder. Unlike certain other HTML5 demo sites, Mozilla's site works in any browser that supports the features used in the demo."

4 of 145 comments (clear)

  1. Interesting link on the history of HTML5 by UnknownSoldier · · Score: 4, Informative

    And why HTML, XHTML, XML, MIME is such a clusterfuck ...

    http://diveintohtml5.org/past.html

  2. Re:What an experience! by multipartmixed · · Score: 3, Informative

    Please turn on the crash reporter and repro!!

    --

    Do daemons dream of electric sleep()?
  3. Re:Graceful degradation? by icebraining · · Score: 4, Informative

    The All-In-One Entirely-Not-Alphabetical No-Bullshit Guide to HTML5 Fallbacks

    --
    Dilbert RSS feed
  4. Re:Web Sockets in Firefox 4 by Aikar · · Score: 2, Informative

    No, it does not. Some inexperienced "security researcher" posted an invalid PDF document placing the fault on WebSockets for a vulnerability in other software. And some Mozilla exec blindly skimmed the document and accepted it as fact and had websockets disabled. But in reality, there fault has absolutely nothing to do with WebSockets, and the fault CAN NOT be fixed in WebSockets. Mozillas suggestion to the problem simply removes the ability to use WebSockets as a vector for the attack, but the attack is still doable by every language on the internet that can create a TCP connection. In other words the exploit is doable on Flash or Java. WebSockets need to be re-enabled ASAP and Mozilla needs to apologize for blindly accepting a document without verifying its credibility. It seriously took me 15 minutes to read the document in full and fully understand the underlying vulnerability and realize it has absolutely nothing to do with WebSockets. Its sad an exec spent less time than that and set their browser back a few years on false grounds. Note: Google was smart and has not disabled WebSockets, maybe cause they RTFD