Slashdot is powered by your submissions, so send in your scoop


Forgot your password?
Firefox Mozilla The Internet

Firefox 16 Released: More HTML5 Support 133

Today Mozilla released the final version of Firefox 16, which includes a number of new tools for developers. "A number of HTML5 code has been 'unprefixed,' which means that Mozilla has decided it has matured enough to run in the browser without causing instability. The newly unshackled HTML5 includes CSS3 Animations, Transforms, Transitions, Image Values, Values and Units, and IndexedDB. Two Web APIs that Mozilla helped to create, Battery API and Vibration API, are also now unprefixed. These changes help keep Firefox competitive, but it also sends a signal to developers that Mozilla thinks these are good enough to begin baking into their sites. It's a strong endorsement of the 'future-Web' tech." Here's the complete change list and the download page.
This discussion has been archived. No new comments can be posted.

Firefox 16 Released: More HTML5 Support

Comments Filter:
  • by c0l0 ( 826165 ) * on Tuesday October 09, 2012 @02:08PM (#41598779) Homepage

    "A number of HTML5 code has been 'unprefixed,' which means that Mozilla has decided it has matured enough to run in the browser without causing instability." - come on, how dumb is that? If there were a vendor-sanctioned CSS attribute or "HTML5 code" (or whatever, really) that was known to cause "instability" in one of the world's most widely-deployed and -used applications, trolls and/or crackers would make ABUNDANT use of that inherent weakness, prefixed or not.

    Now, I don't know for sure how HTML5 "standardization" (if you can stomach calling it that...) actually works, but what I happen to have picked up is this: In reality, that kind of "prefixing" (extending the name of a soon-to-be-"standardized" identifier with a vendor-specific keyword) takes place because the vendor probably still works out implementation details, or isn't 100% sure if he wants to really do whatever the feature/thing is doing right now the way it is doing right now forever. It's some kind of "this is just a draft"-hint, like, for example, "X-"-prefixed HTTP and SMTP header data (used to be - they're abused for other, this-aint-in-the-official-standard-but-we-need-it-anyway-things today, of course). If using any of this causes the browser that implements it to crash or be otherwise unstable (and therefore potentially exploitable), that's a _grave_ bug, and certainly not something that any of the industry heavyweights (well, except for Apple and Microsoft maybe... hehe) would tolerate to occur in the wild for more than a few hours, until an appropriate patch is released.

  • Command line (Score:5, Interesting)

    by buchner.johannes ( 1139593 ) on Tuesday October 09, 2012 @02:13PM (#41598837) Homepage Journal

    The command line [] feature looks very cool. It'd be even better if that could be controlled from outside Firefox, basically making Firefox scriptable -- for automated Firefox testing, Website testing, taking screenshots, etc.

  • by ducomputergeek ( 595742 ) on Tuesday October 09, 2012 @02:19PM (#41598883)

    I know WebSQL got scrubbed from the HTML5 spec a couple years ago, but during that time it got adopted in a usable way by webkit and opera. In the spec or not it's become the defacto standard for anyone doing HTML5 development for mobile devices, especially for use in off-line apps. Not only that, but at this point it's proven and reliable. I have a feeling it's going to be like H.264 vs WebM. The technical gurus will support one over the other due to ideological reasons, meanwhile the rest of us who are being paid to write things that work will continue going on using what works for us and our clients.

    Right now WebSQL is supported on basically 99% of the mobile devices we see in our clients' hands. That includes iOS, Android, Blackberry, hell even Kindle and Nook. On the desktop it works on Safari, Chrome, and hell even FireFox with an extension.

  • by Anonymous Coward on Tuesday October 09, 2012 @02:26PM (#41598955)
    It seems that they're working on it, just extremely slowly. If you open all of the bugs that those two depend on, these are the deepest roots. [] [] The latter was being worked with on Sunday, while the former is lagging with activity, last commented on 3 months ago. You should probably expect it to be fixed in about three years.
  • by narcc ( 412956 ) on Tuesday October 09, 2012 @03:40PM (#41599879) Journal

    Indeed, but not all webkit browsers are equal -- not by a long shot [].

  • by ArhcAngel ( 247594 ) on Tuesday October 09, 2012 @04:09PM (#41600267)
    I have come to prefer Quickjava []. It let's you toggle Java, Javascript, Cookies, Image Animations, Flash, Silverlight, Images, Stylesheets and Proxy quickly. If I encounter a site that is annoying I just toggle the appropriate plugin until I leave that site. The only thing it lacks is the ability to toggle per tab. If it had that it would be perfect.
  • by AndrewStephens ( 815287 ) on Tuesday October 09, 2012 @04:59PM (#41600905) Homepage

    Speaking of HTML5test, I just ran a before and after test with firefox 15 and firefox 16:

    Firefox 15: 346 out of 500
    Firefox 16: 363 out of 500
    Chrome 22: 437 out of 500

  • by Jackie_Chan_Fan ( 730745 ) on Tuesday October 09, 2012 @05:48PM (#41601441)

    Chrome's built in flash player uses 80% cpu on a quadcore where as IE and Firefox use 30% via adobe's on plugin.

    I welcome Firefox 16. I'm sorry I ever left you.

    On the upside, pages with background colors will no longer flash white like they do in chrome. YAY.

    Chrome is bad.

You will never amount to much. -- Munich Schoolmaster, to Albert Einstein, age 10