HTML 5 differences from HTML 4

http://www.w3.org/TR/2008/WD-html5-diff-20080122/

Some interesting stuff, especially the section about New Elements/INPUT

I note also that 'accesskey' has gone from 'button', and a lot of
changes that move attributes & characteristics out of HTML and into CSS.

However I suspect that in plain text e-ail we will still say things like
<b>, <strike> and so forth :slight_smile:

Yeah some extremely interesting stuff in there. I especially like the datetime types on input tags, as well as the required attribute that can be set to indicate a field is required.

Disabling a whole fieldset is nice, so you could toggle the disabled’ness of a fieldset by just toggling this attribute using javascript.

And they’re taking out the frame tag! There is a God!

The align attribute gone from a whole ton of elements, including td AND div. I can imagine a lot of sites breaking now because they’re using this :slight_smile:

I noticed border is now missing from the img tag. Does this mean that when images are created and are inside of a link tag that they will no longer have a border around them, or do they still default to their standard behaviour?

Will be interesting to see it put into play in Firefox 3, Internet Explorer 8 and other browsers.

On Jan 23, 2008 9:40 AM, Anton J Aylward <aja@si.on.ca

The APIs are what struck me most. There are a number of element/attribute changes that will make things easier or break things (depending on where you are in your project). But an API with "persistent storage" is a dramatic departure from the statelessness of HTML. The history is exposed to pages (to fix the Ajax-broke-my-back-button problem and possible to enable the DoubleClick-knows-where-you've-been button).

Lots of other good ideas in terms of creating a declarative platform that's not as dumbed down as we've grown used to. Even more interesting is the notion that HTML 5 may work in disconnected contexts (ala Silverlight and Apollo). If/when this becomes accepted, maybe it would be worth lobbying for pluggable scripting languages. Some of these changes could break Javascript's back (or not, if you're a Javascript ninja).