Skip to content
Browse files
[e] (0) update the intro
git-svn-id: 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed Jun 16, 2011
1 parent 49657ca commit 0fd9df120579d5861dd5eb7ba3b84809694e3e6f
Show file tree
Hide file tree
Showing 3 changed files with 471 additions and 207 deletions.
@@ -282,7 +282,9 @@ <h2 class="no-num no-toc" id=contents>Table of contents</h2>
<ol class=toc>
<li><a href=#introduction><span class=secno>1 </span>Introduction</a>
<li><a href=#is-this-html5?><span class=secno>1.1 </span>Is this HTML5?</a></li>
<li><a href=#is-this-html5?><span class=secno>1.1 </span>Is this HTML5?</a>
<li><a class=notoc href=#how-do-the-whatwg-and-w3c-specifications-differ?><span class=secno>1.1.1 </span>How do the WHATWG and W3C specifications differ?</a></ol></li>
<li><a href=#background><span class=secno>1.2 </span>Background</a></li>
<li><a href=#audience><span class=secno>1.3 </span>Audience</a></li>
<li><a href=#scope><span class=secno>1.4 </span>Scope</a></li>
@@ -929,7 +931,7 @@ <h2 class="no-num no-toc" id=contents>Table of contents</h2>
<li><a href=#killing-scripts><span class=secno> </span>Killing scripts</a></li>
<li><a href=#runtime-script-errors><span class=secno> </span>Runtime script errors</a>
<li><a href=#runtime-script-errors><span class=secno> </span>Runtime script errors in documents</a></ol></ol></li>
<li><a href=#runtime-script-errors-in-documents><span class=secno> </span>Runtime script errors in documents</a></ol></ol></li>
<li><a href=#event-loops><span class=secno>7.1.4 </span>Event loops</a>
<li><a href=#definitions-1><span class=secno> </span>Definitions</a></li>
@@ -1379,18 +1381,182 @@ <h3 id=is-this-html5?><span class=secno>1.1 </span>Is this HTML5?</h3>

<p><i>This section is non-normative.</i></p>

<p>In short: Yes.</p>

<p>No, although it does contain everything that is part of HTML5. If
you want only HTML5, please see <a href=>the HTML specification</a>.</p>
<p>In more length: The term "HTML5" is widely used as a buzzword to
refer to modern Web technologies, many of which (though by no means
all) are developed at the WHATWG, in some cases in conjunction with
the W3C and IETF.</p>

<p><em>This</em> specification contains everything that the WHATWG
is actively working on. For more details, please see <a href=>the
relevant FAQ entry</a>.</p>
<p>The WHATWG work is all published in one specification

(the one you are reading right now),

parts of which are republished in a variety of other forms,
including an edition optimized for Web developers

(known as <a href=>HTML5</a>),

<h3 id=background><span class=secno>1.2 </span>Background</h3>

and one which focuses mainly on the core HTML language

(known as the <a href=>HTML Living Standard</a>).

In addition, two subparts of the specification are republished as
separate documents, for ease of reference:
<a href=>WebVTT</a>
<a href=>WebRTC</a>.

<p>The W3C also publishes parts of this specification as separate
documents. One of these parts is called "HTML5"; it is a subset of

the <a href=>HTML
Living Standard</a>.</p>

<p>The WHATWG specification is a continuously maintained living
standard, with maturity managed at a very granular per-section
scale, indicated by markers in the left margin; this is intended to
model the way in which specifications are approached in practice by
implementors and authors alike. The W3C specifications follow a more
traditional style, with versioned releases of the specification, and
with maturity management being done only at the document level; this
means that the W3C specifications have version numbers (e.g.
"HTML5") and necessarily go through periods of "feature freeze"
where new features are not added, so that the specifications can as
a whole reach a more mature state.</p>

<h6 class=notoc id=how-do-the-whatwg-and-w3c-specifications-differ?><span class=secno>1.1.1 </span>How do the WHATWG and W3C specifications differ?</h6>

<p>The features present in both the WHATWG and W3C specifications
are specified using identical text, except for the following (mostly
editorial) differences:</p><!--FORK-->

<li>Instead of this section, the W3C HTML specification has a
different paragraph explaining the difference between the W3C and
WHATWG versions of HTML.</li>
--><!-- in the status section --><li>The W3C HTML specification refers to the technology as HTML5,
rather than just HTML.</li><!--VERSION-->

<li>Examples that use features from HTML5 are not present in the
W3C specifications since the W3C specifications are published as
HTML4 due to <a href=";uri=#format">W3C
publication policies</a>.</li><!--HTML4POLICE-->

<li>The W3C HTML specification defines conformance for documents in
a more traditional (version-orientated) way, because of <a href=>a
working group decision from March 2011</a>. This specification, in
part driven by its versionless development model, instead uses a
conformance definition that more closely models how specifications
are used in practice.</li><!--CONFORMANCE-->

<li>The W3C HTML specification omits a paragraph of implementation
advice because of <a href=>a
working group decision from June 2010</a>.</li>

<li>The W3C HTML specification includes a paragraph of advice
redundant with the ARIA specifications because of <a href=>a
working group decision from March 2011</a>.</li>

<li>The W3C HTML specification gives incomplete advice regarding
the <code title=attr-img-alt><a href=#attr-img-alt>alt</a></code> attribute and instead
references other documents on the matter because of <a href=>a
working group decision from March 2011</a>.</li>

<li>The W3C HTML specification includes a link to an incomplete
document that contradict this specification because of <a href=>a
working group decision from Februray 2011</a>.</li><!--HPAAIG-->

<li>The W3C HTML specification has different prose regarding the
use of tables for layout purposes because of <a href=>a
working group decision from March 2011</a>. In contrast, this
specification unambiguously disallows the use of <code><a href=#the-table-element>table</a></code>
elements for layout purposes.</li>

<li>The W3C HTML specification requires authors who are writing
HTML e-mails with images to people they know can see the images
(e.g. a wife sending her husband photos of their child) to
nonetheless include textual alternatives to those images, because
of <a href=>a
working group decision from April 2011</a>.</li>

<li>The W3C HTML specification does not state that the
<code><a href=#the-img-element>img</a></code> element's <code title=attr-img-alt><a href=#attr-img-alt>alt</a></code>
attribute is its <a href=#fallback-content>fallback content</a>, because of <a href=>a
working group decision from April 2011</a>.</li>

<li>The W3C HTML specification is missing a clause that requires
conformance checkers to discourage cargo-cult accessibility
authoring because of <a href=>a
working group chair decision from May 2011</a>.</li><!--bug

<li>The W3C HTML specification is missing some conformance
constraints that would make documents misusing <code><a href=#the-canvas-element>canvas</a></code>
invalid, because of <a href=>a
working group chair decision from June 2011</a>.</li><!--bug

<li>The W3C 2D Context specification has a different API for
handling focus and selection in the 2D canvas API, because of <a href=>a
working group chair decision from May 2011</a>.</li>

</ul><p>The following sections are only published in the WHATWG
specifications and are not currently available anywhere else:</p>

<ul><li>The <code><a href=#peerconnection>PeerConnection</a></code> API and related video-conferencing features.</li> <!--PEERCONNECTION-->
<li>The <code title=attr-hyperlink-ping><a href=#ping>ping</a></code> attribute and related <a href=#hyperlink-auditing>hyperlink auditing</a> features.</li> <!--PING-->
<li>The <a href=#webvtt>WebVTT</a> format and some <a href=#text-track>text track</a> API features.</li> <!--TTVTT-->
<li>Rules for <a href=#atom>converting HTML to Atom</a>.</li> <!--MD-->
<li>The <code title=dom-document-cssElementMap><a href=#dom-document-csselementmap>cssElementMap</a></code> feature for defining <span title="CSS element reference identifier">CSS element reference identifiers</span>.</li> <!--CSSREF-->
<li>An experimental <code><a href=#undomanager>UndoManager</a></code> interface.</li><!--UNDO-->
<li>Some predefined <a href=#mdvocabs>Microdata vocabularies</a>.</li>
<p>Features that are part of the WHATWG HTML Living Standard
specification but that are currently published as separate
specifications as well, and are not included in the W3C HTML5
specification, consist of:</p>

<li><a href="#2dcontext">Canvas 2D Graphics Context</a>--><!--2DCONTEXT--><!--
<li><a href="#microdata">Microdata</a>--><!--MD--><!--
<li><a href="#crossDocumentMessages">Cross-document messaging</a> (also known as Communications)--><!--POSTMSG--><!--
<li><a href="#channel-messaging">Channel messaging</a> (also known as Communications)--><!--POSTMSG--><!--
<h6 class="notoc">What else is HTML5?</h6>

<p>Features that are not currently published or maintained by the
WHATWG but that are sometimes considered to be informally part of
"HTML5" include:</p>

<li><a href="">WebSocket protocol</a>
<li><a href="">Media Type Sniffing</a>
<li><a href="">The Web Origin Concept</a>
<li><a href="">Geolocation API</a>
<li><a href="">SVG</a>
<li><a href="">MathML</a>
<li><a href="">XMLHttpRequest</a>
<li>Parts of <a href="">CSS</a>.</li>
<p>The <a href="#forms">forms</a> part of this specification was
previously published separately in a specification known as Web
Forms 2. The <a href="#workers">Web Workers</a> section was also
previously published as a separate document.</p>
<p>See also <a
relevant FAQ entry</a>.</p>
--><!--VERSION--><h3 id=background><span class=secno>1.2 </span>Background</h3>

<p><i>This section is non-normative.</i></p>

@@ -67474,7 +67640,7 @@ <h5 id=runtime-script-errors><span class=secno> </span>Runtime script err


</dl><h6 id=runtime-script-errors><span class=secno> </span>Runtime script errors in documents</h6>
</dl><h6 id=runtime-script-errors-in-documents><span class=secno> </span>Runtime script errors in documents</h6>

<p>Whenever an uncaught runtime script error occurs in one of the
scripts associated with a <code><a href=#document>Document</a></code>, the user agent must

0 comments on commit 0fd9df1

Please sign in to comment.