
Hypertext Markup Language (HTML) 5 introduces new elements to HTML for the first time since the last millennium. New structural elements include aside, figure, and section. New inline elements include time, meter, and progress. New embedding elements include video and audio. New interactive elements include details, datagrid, and command.
Three major browser vendors—Apple, Opera, and the Mozilla Foundation—came together as the Web Hypertext Application Technology Working Group (WhatWG) to develop an updated and upgraded version of classic HTML. More recently, the W3C took note of these developments and started its own next-generation HTML effort with many of the same members. Eventually, the two efforts will likely be merged. Although many details remain to be argued over, the outlines of the next version of HTML are becoming clear.
Finally some progress. Although I don't think this brings us a huge step closer to much better web applications. Mozilla was far ahead of the game when they came up with XUL.
Microsoft will still find a way to monkey with it, I bet. They'll put some kind of "Premium Content Rights Management" on the last 50 characters of text in a div or something.
They're usual tactic is to not exactly conform to the standard, but close enough where developers will make little tweaks so their stuff works with Microsoft software. Although with IE market share lower I'm not sure how well that would work these days.
HTML 5? I thought W3C was discontinuing HTML in favor of XHTML.
It seems the WhatWG group made enough noise and got enough attention that the W3C decided to not ignore it any longer. At least that's my interpretation.
Think I'll stick with XHTML, after all I already bought the books and everything. Plus it's nice to be able to validate web pages with XML Spy.
Already wobbly from an unwillingness or inabilty to meet real-world needs of real-world developers, xhtml fell over and rotted under the weight of its own bulk. It was, however pushed by certain browser vendor that still hasn't properly supported it.
I'm looking forward to html 5. Looks like there's a lot of things in there that solve a lot of real problems. If nothing else, validation will be a big plus.
The HTML5 spec also specs out XHTML5, but it must be served as xml. So you can still use XHTML is you want, but it will probably be read as tag soup as it is today (unless IE decided XML is a good thing).
Not sold yet on the idea of HTML 5, it's main purpose is to make it easier for non-programmers to write websites?
I've always found the idea of content and structure being separate a useful thing, this would reverse that effort and restructure content. It's certainly not perfect today but it's much closer than this appears.
I'm waiting to pass judgment until I see how it's implemented in each browser. We may end up with some really great new features or a complete mess.
For example,you might attach background music to a Web page like this
NOOOOOOOOOO!!!
I'm all for the proposed semantic changes in HTML5. Most folks who write semantic code already do something like this (with a class or an id), and this just shortens it.
I do agree with you, Kyle, about keeping structure and presentation separately. I hope they deprecate crud like hspace & vspace, cellspacing, cellpadding, etc. as all of that can be handled by margin, padding, and more in CSS.
Overall, though, it does look pretty exciting.
Damian, you bring up a good point. I'd like to see deprecated features removed and no longer supported. If a document claims to be HTML5 it shouldn't have any deprecated attributes like align. If the document is defined as HTML4 or below then of course it could still have those features.
Kyle, it's not so much aimed at making things easier as it's attempting to address some long overdue issues. The HTML5 folks wouldn't suggest anything less than separation of content and presentation.
But serving up xhtml as html is a joke. Many people (myself included) do it, but that doesnt' make it any less of a joke.
They felt xhtml wasn't going to be properly supported anytime in the near future, xhtml 2.0 (and 1.1) are going nowhere, and moving forward with html would be more effective. At this point, I agree.
For example,you might attach background music to a Web page like this
NOOOOOOOOOO!!!
Oh, c'mon. It'll be retro like the late 90s. We can embed MIDI tracks of The Chicken Polka.
I prefer the Hamster Dance.
"dee de dee dee dee...."
Actually, looking at the W3C's New Elements in HTML 5, it's pretty damn exciting. It looks like a lot of what currently requires javascript or php can be done strictly with HTML (e.g., check out someof the new attributes for the input element's type attribute).
And the semantic tags being added are going to make my life easier—hell, the dialog one alone is worth it. And they're finally deprecating u.
Kewl...
Not before time to. I'm sure there will be a problem though with some browsers. I bet my much loved Firefox won't have any issues though.
Spuds, what browsers are you referring to? With the exception of some hackery here and there, browsers as far back as IE5 work well with HTML & CSS. I typically only try to go back as far as 5.5, though. I'm not supporting something older than 7 years.
I think he's referring to Firefox and Safari often conforming to the latest standards first while IE usually lags behind. Until Firefox gained a lot of popularity Microsoft didn't bother putting out significantly newer versions of IE for years.
I love speculation as to just what I am talking about. Matt you are exactly right.
You're in Easy Mode. If you prefer, you can use XHTML Mode instead. |