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! There are
also some spec-wide issues that have not yet been addressed:
case-sensitivity is a very poorly handled topic right now, and the firing
of events needs to be unified (right now some bubble, some don't, they all
use different text to fire events, etc). It would also be nice to unify
the rules on downloading content when attributes change (e.g. src attributes) - should they initiate downloads when the
element immediately, is inserted in the document, when active scripts end,
etc. This matters e.g. if an attribute is set twice in a row (does it hit
the network twice).
a
element
q
element
cite element
em element
strong element
small element
mark element
dfn element
abbr element
time element
progress element
meter element
code element
var element
samp element
kbd element
sub and sup elements
span element
i element
b element
bdo element
ruby element
rt element
rp element
figure element
img element
iframe element
embed element
object element
param element
video element
audio element
source element
canvas element
canvas elements
map element
area element
table element
caption element
colgroup element
col element
tbody element
thead element
tfoot element
tr element
td element
th element
td and th elements
form element
fieldset element
input element
button element
label element
select element
datalist element
optgroup element
option element
textarea element
output element
details element
datagrid element
datagrid data model
datagrid element
datagrid
command element
bb element
menu element
a element to define a command
button element to define a command
input element to define a command
option element to define a command
command element to define a command
bb element to define a command
alternate"
archives"
author"
bookmark"
external"
feed"
help"
icon"
license"
nofollow"
noreferrer"
pingback"
prefetch"
search"
stylesheet"
sidebar"
tag"
irrelevant attribute
contenteditable attribute