You can take part in this work. Join the working group's discussion list.
Web designers! We have a FAQ, a forum, and a help mailing list for you!
© Copyright 2004-2008 Apple Computer, Inc., Mozilla Foundation, and Opera Software ASA.
You are granted a license to use, reproduce and create derivative works of this document.
This specification evolves HTML and its related APIs to ease the authoring of Web-based applications. Additions include context menus, a direct-mode graphics canvas, a full duplex client-server communication channel, more semantics, audio and video, various features for offline Web applications, sandboxed iframes, and scoped styling. Heavy emphasis is placed on keeping the language backwards compatible with existing legacy user agents and on keeping user agents backwards compatible with existing legacy documents.
This is a work in progress! This document is changing on a daily if not hourly basis in response to comments and as a general part of its development process. Comments are very welcome, please send them to whatwg@whatwg.org. Thank you.
The current focus is in responding to the outstanding feedback. (There is a chart showing current progress.)
Implementors should be aware that this specification is not stable. Implementors who are not taking part in the discussions are likely to find the specification changing out from under them in incompatible ways. Vendors interested in implementing this specification before it eventually reaches the call for implementations should join the WHATWG mailing list and take part in the discussions.
This specification is also being produced by the W3C HTML WG. The two specifications are identical from the table of contents onwards.
This specification is intended to replace (be the new version of) what was previously the HTML4, XHTML 1.x, and DOM2 HTML specifications.
Different parts of this specification are at different levels of maturity.
Some of the more major known issues are marked like this. There are many other issues that have been raised as well; the issues given in this document are not the only known issues! Also, firing of events needs to be unified (right now some bubble, some don't, they all use different text to fire events, etc).
a elementq elementcite elementem elementstrong elementsmall elementmark elementdfn elementabbr elementtime elementprogress elementmeter elementcode elementvar elementsamp elementkbd elementsub and sup elementsspan elementi elementb elementbdo elementruby elementrt elementrp elementfigure elementimg element
iframe elementembed elementobject elementparam elementvideo element
audio element
source elementcanvas element
canvas elementsmap elementarea elementtable elementcaption elementcolgroup elementcol elementtbody elementthead elementtfoot elementtr elementtd elementth elementtd and th elementsform elementfieldset elementlabel elementinput element
type attribute
input element attributes
autocomplete attributelist attributereadonly attributesize attributerequired attributemultiple attributemaxlength attributepattern attributemin and max attributesstep attributeplaceholder attributeinput element APIsbutton elementselect elementdatalist elementoptgroup elementoption elementtextarea elementoutput elementdetails elementdatagrid element
datagrid data modeldatagrid elementdatagridcommand elementbb element
menu element
a element to define a commandbutton element to define a commandinput element to define a commandoption element to define a commandcommand element to define
a commandbb element to define a commandalternate"archives"author"bookmark"external"feed"help"icon"license"nofollow"noreferrer"pingback"prefetch"search"stylesheet"sidebar"tag"hidden attributecontenteditable attribute