HTML 5 is another guess at the future

http://www.bigcontrarian.com/2009/09/04/tagged/

by maryrosecook • 17 years ago

29 9 17 years ago

danw• 17 years ago

See Douglas Crockford's suggestion for HTML5 at http://www.crockford.com/html/

hvs3• 17 years ago

That's actually similar to what I was thinking. Making HTML5 support generic tags and attributes that could be defined as first-class elements would completely eliminate the need to create a huge pile of new tags. This would allow for much more innovation while not limiting the design to some arbitrary set of new elements. Instead of thinking of HTML as a "document format", it should be thought of as a display interface with a low-level protocol for interaction.

tumult• 17 years ago

so you're going to implement <video> in javascript?

rimantas• 17 years ago

Well, all those points were discussed and there are sound reasons why they are as they are in HTML5

Versioning — it just does not make any sense. Browsers render web content to their abilities, not by spec. Some my not support parts of HTML4 but support other parts from HTML five.

No doctype — creators of HTML5 would be glad to get rid of it, alas, it is required to force browsers to use standards compliant rendering mode. Without doctype they fall back to quirks mode, which is bad.

CSS — unified rendering would be nice, but that's not the subject of HTML spec. And reset stylesheets are just plain stupid.

Self closing <script> — historical reasons… :)

Custom tags — what? You can invent any tags you like and modern browsers will allow you to style them. If you want custom tags, you don't need a spec. The point of the spec to define agreement on what which elements means.

Custom attributes: HTML5 has that in the form of data-* attributes and elements get element.dataset accessor.

pkulak• 17 years ago

I understand his argument that what we've got works now, so who cares, but it doesn't work for _everyone_. I'm sure people with screen readers (it's the header because it's darker and that's the nav bar because it's got that box around it, duh!) would really appreciate some standard way to know what's what on the page.

HTML 5 is another guess at the future

Related Stories