Ding Dong the Frame is dead

So the W3C released a draft of HTML5 and I tried to get excited but there wasn’t a lot there really to grab my attention – well there was one thing – no more damn frames. It’s got to be worthwhile upgrading just to see the end of that filth 🙂
From a structural perspective most of the formatting constructs have been removed or more correctly delegated to the CSS. As such HTML5 is structurally far simpler than HTML4 so that has to be a good thing.

Has anything interesting been added to HTML5 in the *gasp* nearly 10 years since HTML 4.01?

Well there are some good web application constructs, such as :

  • 2D drawing API which can be used with the new canvas element.
  • API for playing of video and audio which can be used with the new video and audio elements.
  • Persistent storage. Both key / value and a SQL database are supported.
  • An API that enables offline Web applications.
  • An API that allows a Web application to register itself for certain protocols or MIME types.
  • Editing API in combination with a new global contenteditable attribute.
  • Drag & drop API in combination with a draggable attribute.
  • Network API.
  • API that exposes the history and allows pages to add to it to prevent breaking the back button. (This API has the necessary security restrictions in place.)
  • Cross-document messaging.
  • Server-sent events in combination with the new event-source element.

In summary, some stuff that may make the development of web 2.0 applications a bit easier and hopefully allow some of them to suck less but how long do we have to wait for this draft to turn into something concrete – 2010 . Too little, too late. Give me more – but feel free to take the frame away right now.


2 thoughts on “Ding Dong the Frame is dead

  1. What more would you like?

    You’re free to join the HTML WG, and I strongly invite you to do so if you have any proposals regarding HTML 5.

  2. This is an excellent outline. Thanks. Consider also that HTML5’s Persistent Offline Storage is significant information security and risk management challenges. I believe that it is going to materially increase the importance of effectively sanitizing inputs and encoding outputs to resist XSS — and the new types of damage that can be caused when they are directed against persistent offline storage. See a longer version of this argument at: http://completosec.wordpress.com/2010/02/07/html-5-persistent-offline-storage-as-a-risk-management-challenge/.
    Matt McCright

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s