W3C home > Mailing lists > Public > public-html-commits@w3.org > April 2011

html5/spec-author-view full-spec.html,NONE,1.1 Makefile,1.46,1.47 association-of-controls-and-forms.html,1.416,1.417 dnd.html,1.419,1.420 editing.html,1.974,1.975 edits.html,1.411,1.412 forms.html,1.969,1.970 index.html,1.985,1.986 interactive-elements.html,1.970,1.971 introduction.html,1.977,1.978 offline.html,1.970,1.971 spec.html,1.1381,1.1382 tabular-data.html,1.962,1.963 text-level-semantics.html,1.978,1.979 the-map-element.html,1.419,1.420 video.html,1.993,1.994

From: Michael Smith via cvs-syncmail <cvsmail@w3.org>
Date: Sat, 23 Apr 2011 01:54:20 +0000
To: public-html-commits@w3.org
Message-Id: <E1QDS3A-00012M-Ie@lionel-hutz.w3.org>
Update of /sources/public/html5/spec-author-view
In directory hutz:/tmp/cvs-serv3874

Modified Files:
	Makefile association-of-controls-and-forms.html dnd.html 
	editing.html edits.html forms.html index.html 
	interactive-elements.html introduction.html offline.html 
	spec.html tabular-data.html text-level-semantics.html 
	the-map-element.html video.html 
Added Files:
	full-spec.html 
Log Message:
Fix a few places where a media element could get out of sync with its controller, and re-enable media fragments for loading resources with a controller. (whatwg r6025)

[updated by splitter]


Index: text-level-semantics.html
===================================================================
RCS file: /sources/public/html5/spec-author-view/text-level-semantics.html,v
retrieving revision 1.978
retrieving revision 1.979
diff -u -d -r1.978 -r1.979
--- text-level-semantics.html	22 Apr 2011 19:54:36 -0000	1.978
+++ text-level-semantics.html	23 Apr 2011 01:54:18 -0000	1.979
@@ -1840,7 +1840,7 @@
    <pre>&lt;p&gt;So then he pointed at the tiger and screamed
 "there&lt;wbr&gt;is&lt;wbr&gt;no&lt;wbr&gt;way&lt;wbr&gt;you&lt;wbr&gt;are&lt;wbr&gt;ever&lt;wbr&gt;going&lt;wbr&gt;to&lt;wbr&gt;catch&lt;wbr&gt;me"!&lt;/p&gt;</pre>
 
-  </div><h4 id="usage-summary"><span class="secno">4.6.28 </span>Usage summary</h4><p><i>This section is non-normative.</i><table><thead><tr><th>Element
+  </div><h4 id="usage-summary"><span class="secno">4.6.28 </span>Usage summary</h4><table><thead><tr><th>Element
      <th>Purpose
      <th>Example
    <tbody><tr><td><code><a href="#the-a-element" id="a_19">a</a></code>

Index: the-map-element.html
===================================================================
RCS file: /sources/public/html5/spec-author-view/the-map-element.html,v
retrieving revision 1.419
retrieving revision 1.420
diff -u -d -r1.419 -r1.420
--- the-map-element.html	22 Apr 2011 19:54:37 -0000	1.419
+++ the-map-element.html	23 Apr 2011 01:54:18 -0000	1.420
@@ -486,13 +486,13 @@
      <th>Keywords
      <tbody><tr><td rowspan="2"><a href="#attr-area-shape-circle" id="attr-area-shape-circle_0" title="attr-area-shape-circle">Circle state</a>
      <td><dfn id="attr-area-shape-keyword-circle" title="attr-area-shape-keyword-circle"><code>circle</code></dfn>
-     <tr><td><a href="#attr-area-shape-default" id="attr-area-shape-default_0" title="attr-area-shape-default">Default state</a>
+     <tr><tr><td><a href="#attr-area-shape-default" id="attr-area-shape-default_0" title="attr-area-shape-default">Default state</a>
      <td><dfn id="attr-area-shape-keyword-default" title="attr-area-shape-keyword-default"><code>default</code></dfn>
      <tr><td rowspan="2"><a href="#attr-area-shape-poly" id="attr-area-shape-poly_0" title="attr-area-shape-poly">Polygon state</a>
      <td><dfn id="attr-area-shape-keyword-poly" title="attr-area-shape-keyword-poly"><code>poly</code></dfn>
-     <tr><td rowspan="2"><a href="#attr-area-shape-rect" id="attr-area-shape-rect_0" title="attr-area-shape-rect">Rectangle state</a>
+     <tr><tr><td rowspan="2"><a href="#attr-area-shape-rect" id="attr-area-shape-rect_0" title="attr-area-shape-rect">Rectangle state</a>
      <td><dfn id="attr-area-shape-keyword-rect" title="attr-area-shape-keyword-rect"><code>rect</code></dfn>
-     </table><p>The attribute may be omitted. The <i>missing value default</i> is
+     <tr></table><p>The attribute may be omitted. The <i>missing value default</i> is
   the <a href="#attr-area-shape-rect" id="attr-area-shape-rect_1" title="attr-area-shape-rect">rectangle</a> state.<p>The <dfn id="attr-area-coords" title="attr-area-coords"><code>coords</code></dfn>
   attribute must, if specified, contain a <a href="common-microsyntaxes.html#valid-list-of-integers" id="valid-list-of-integers_0">valid list of
   integers</a>. This attribute gives the coordinates for the shape

Index: tabular-data.html
===================================================================
RCS file: /sources/public/html5/spec-author-view/tabular-data.html,v
retrieving revision 1.962
retrieving revision 1.963
diff -u -d -r1.962 -r1.963
--- tabular-data.html	22 Apr 2011 19:54:36 -0000	1.962
+++ tabular-data.html	23 Apr 2011 01:54:17 -0000	1.963
@@ -1171,7 +1171,7 @@
 
    </dd>
 
-  </dl><h4 id="examples"><span class="secno">4.9.12 </span>Examples</h4><p><i>This section is non-normative.</i><p>The following shows how might one mark up the bottom part of
+  </dl><h4 id="examples"><span class="secno">4.9.12 </span>Examples</h4><p>The following shows how might one mark up the bottom part of
   table 45 of the <cite>Smithsonian physical tables, Volume
   71</cite>:<pre>&lt;table&gt;
  &lt;caption&gt;Specification values: &lt;b&gt;Steel&lt;/b&gt;, &lt;b&gt;Castings&lt;/b&gt;,

Index: association-of-controls-and-forms.html
===================================================================
RCS file: /sources/public/html5/spec-author-view/association-of-controls-and-forms.html,v
retrieving revision 1.416
retrieving revision 1.417
diff -u -d -r1.416 -r1.417
--- association-of-controls-and-forms.html	22 Apr 2011 19:54:27 -0000	1.416
+++ association-of-controls-and-forms.html	23 Apr 2011 01:54:14 -0000	1.417
@@ -697,7 +697,7 @@
   hostile users, and unintentionally bypassed by users of older user
   agents or automated tools that do not implement these features. The
   constraint validation features are only intended to improve the user
-  experience, not to provide any kind of security mechanism.<h4 id="form-submission"><span class="secno">4.10.22 </span><dfn>Form submission</dfn></h4><p><i>This section is non-normative.</i><p>When a form is submitted, the data in the form is converted into
+  experience, not to provide any kind of security mechanism.<h4 id="form-submission"><span class="secno">4.10.22 </span><dfn>Form submission</dfn></h4><p>When a form is submitted, the data in the form is converted into
   the structure specified by the <a href="#concept-fs-enctype" id="concept-fs-enctype_1" title="concept-fs-enctype">enctype</a>, and then sent to the
   destination specified by the <a href="#concept-fs-action" id="concept-fs-action_0" title="concept-fs-action">action</a> using the given <a href="#concept-fs-method" id="concept-fs-method_1" title="concept-fs-method">method</a>.<p>For example, take the following form:<pre>&lt;form action="/find.cgi" method=get&gt;
  &lt;input type=text name=t&gt;

Index: forms.html
===================================================================
RCS file: /sources/public/html5/spec-author-view/forms.html,v
retrieving revision 1.969
retrieving revision 1.970
diff -u -d -r1.969 -r1.970
--- forms.html	22 Apr 2011 19:54:28 -0000	1.969
+++ forms.html	23 Apr 2011 01:54:14 -0000	1.970
@@ -344,7 +344,7 @@
     <ol><li><a href="forms.html#introduction-0"><span class="secno">4.10.1 </span>Introduction</a>
       <ol><li><a href="forms.html#writing-a-form-s-user-interface"><span class="secno">4.10.1.1 </span>Writing a form's user interface</a><li><a href="forms.html#implementing-the-server-side-processing-for-a-form"><span class="secno">4.10.1.2 </span>Implementing the server-side processing for a form</a><li><a href="forms.html#configuring-a-form-to-communicate-with-a-server"><span class="secno">4.10.1.3 </span>Configuring a form to communicate with a server</a><li><a href="forms.html#client-side-form-validation"><span class="secno">4.10.1.4 </span>Client-side form validation</a></ol><li><a href="forms.html#categories"><span class="secno">4.10.2 </span>Categories</a><li><a href="forms.html#the-form-element" id="x4.10.3-the-form-element"><span class="secno">4.10.3 </span>The <code>form</code> element</a><li><a href="forms.html#the-fieldset-element" id="x4.10.4-the-fieldset-element"><span class="secno">4.10.4 </span>The <code>fieldset</code> element</a><li><a href="forms.html#the-legend-element" id="x4.10.5-the-legend-element"><span class="secno">4.10.5 </span>The <code>legend</code> element</a><li><a href="forms.html#the-label-element" id="x4.10.6-the-label-element"><span class="secno">4.10.6 </span>The <code>label</code> element</a></ol></ol></ol></div>
 
-  <h3 id="forms"><span class="secno">4.10 </span>Forms</h3><h4 id="introduction-0"><span class="secno">4.10.1 </span>Introduction</h4><p><i>This section is non-normative.</i><p>A form is a component of a Web page that has form controls, such
+  <h3 id="forms"><span class="secno">4.10 </span>Forms</h3><h4 id="introduction-0"><span class="secno">4.10.1 </span>Introduction</h4><p>A form is a component of a Web page that has form controls, such
   as text fields, buttons, checkboxes, range controls, or color
   pickers. A user can interact with such a form, providing data that
   can then be sent to the server for further processing (e.g.
@@ -354,7 +354,7 @@
   purposes other than submitting data to a server.<p>Writing a form consists of several steps, which can be performed
   in any order: writing the user interface, implementing the
   server-side processing, and configuring the user interface to
-  communicate with the server.<h5 id="writing-a-form-s-user-interface"><span class="secno">4.10.1.1 </span>Writing a form's user interface</h5><p><i>This section is non-normative.</i><p>For the purposes of this brief introduction, we will create a
+  communicate with the server.<h5 id="writing-a-form-s-user-interface"><span class="secno">4.10.1.1 </span>Writing a form's user interface</h5><p>For the purposes of this brief introduction, we will create a
   pizza ordering form.<p>Any form starts with a <code><a href="#the-form-element" id="form_12">form</a></code> element, inside which
   are placed the controls. Most controls are represented by the
   <code><a href="the-input-element.html#the-input-element" id="input_46">input</a></code> element, which by default provides a one-line
@@ -488,7 +488,7 @@
  &lt;p&gt;&lt;label&gt;Preferred delivery time: &lt;input type=time min="11:00" max="21:00" step="900"&gt;&lt;/label&gt;&lt;/p&gt;
  &lt;p&gt;&lt;label&gt;Delivery instructions: &lt;textarea&gt;&lt;/textarea&gt;&lt;/label&gt;&lt;/p&gt;
 <strong> &lt;p&gt;&lt;button&gt;Submit order&lt;/button&gt;&lt;/p&gt;</strong>
-&lt;/form&gt;</pre><h5 id="implementing-the-server-side-processing-for-a-form"><span class="secno">4.10.1.2 </span>Implementing the server-side processing for a form</h5><p><i>This section is non-normative.</i><p>The exact details for writing a server-side processor are out of
+&lt;/form&gt;</pre><h5 id="implementing-the-server-side-processing-for-a-form"><span class="secno">4.10.1.2 </span>Implementing the server-side processing for a form</h5><p>The exact details for writing a server-side processor are out of
   scope for this specification. For the purposes of this introduction,
   we will assume that the script at <code title="">https://pizza.example.com/order.cgi</code> is configured to
   accept submissions using the <code title="attr-fs-enctype-urlencoded"><a href="association-of-controls-and-forms.html#attr-fs-enctype-urlencoded" id="application-x-www-form-urlencoded">application/x-www-form-urlencoded</a></code>
@@ -514,7 +514,7 @@
    <dt><code title="">comments</code></dt>
    <dd>The delivery instructions</dd>
 
-  </dl><h5 id="configuring-a-form-to-communicate-with-a-server"><span class="secno">4.10.1.3 </span>Configuring a form to communicate with a server</h5><p><i>This section is non-normative.</i><p>Form submissions are exposed to servers in a variety of ways,
+  </dl><h5 id="configuring-a-form-to-communicate-with-a-server"><span class="secno">4.10.1.3 </span>Configuring a form to communicate with a server</h5><p>Form submissions are exposed to servers in a variety of ways,
   most commonly as HTTP GET or POST requests. To specify the exact
   method used, the <code title="attr-fs-method"><a href="association-of-controls-and-forms.html#attr-fs-method" id="method">method</a></code>
   attribute is specified on the <code><a href="#the-form-element" id="form_13">form</a></code> element. This
@@ -559,7 +559,7 @@
   e-mail address, asked for a medium-sized pizza, selected the Extra
   Cheese and Mushroom toppings, entered a delivery time of 7pm, and
   left the delivery instructions text field blank, the user agent
-  would submit the following to the online Web service:<pre>custname=Denise+Lawrence&amp;custtel=555-321-8624&amp;custemail=&amp;size=medium&amp;topping=cheese&amp;topping=mushroom&amp;delivery=19%3A00&amp;comments=</pre><h5 id="client-side-form-validation"><span class="secno">4.10.1.4 </span>Client-side form validation</h5><p><i>This section is non-normative.</i><p>Forms can be annotated in such a way that the user agent will
+  would submit the following to the online Web service:<pre>custname=Denise+Lawrence&amp;custtel=555-321-8624&amp;custemail=&amp;size=medium&amp;topping=cheese&amp;topping=mushroom&amp;delivery=19%3A00&amp;comments=</pre><h5 id="client-side-form-validation"><span class="secno">4.10.1.4 </span>Client-side form validation</h5><p>Forms can be annotated in such a way that the user agent will
   check the user's input before the form is submitted. The server
   still has to verify the input is valid (since hostile users can
   easily bypass the form validation), but it allows the user to avoid

Index: interactive-elements.html
===================================================================
RCS file: /sources/public/html5/spec-author-view/interactive-elements.html,v
retrieving revision 1.970
retrieving revision 1.971
diff -u -d -r1.970 -r1.971
--- interactive-elements.html	22 Apr 2011 19:54:30 -0000	1.970
+++ interactive-elements.html	23 Apr 2011 01:54:15 -0000	1.971
@@ -568,7 +568,7 @@
   attribute gives the label of the menu. It is used by user agents to
   display nested menus in the UI. For example, a context menu
   containing another menu would use the nested menu's <code title="attr-menu-label"><a href="#attr-menu-label" id="label_40">label</a></code> attribute for the submenu's
-  menu label.<h5 id="menus-intro"><span class="secno">4.11.4.1 </span>Introduction</h5><p><i>This section is non-normative.</i><p>The <code><a href="#menus" id="menu_17">menu</a></code> element is used to define context menus and
+  menu label.<h5 id="menus-intro"><span class="secno">4.11.4.1 </span>Introduction</h5><p>The <code><a href="#menus" id="menu_17">menu</a></code> element is used to define context menus and
   toolbars.<p>For example, the following represents a toolbar with three menu
   buttons on it, each of which has a dropdown menu with a series of
   options:<pre>&lt;menu type="toolbar"&gt;

Index: editing.html
===================================================================
RCS file: /sources/public/html5/spec-author-view/editing.html,v
retrieving revision 1.974
retrieving revision 1.975
diff -u -d -r1.974 -r1.975
--- editing.html	22 Apr 2011 19:54:28 -0000	1.974
+++ editing.html	23 Apr 2011 01:54:14 -0000	1.975
@@ -475,7 +475,7 @@
 
    </dd>
 
-  </dl><h3 id="assigning-keyboard-shortcuts"><span class="secno">7.4 </span>Assigning keyboard shortcuts</h3><h4 id="introduction-5"><span class="secno">7.4.1 </span>Introduction</h4><p><i>This section is non-normative.</i><p>Each element that can be activated or focused can be assigned a
+  </dl><h3 id="assigning-keyboard-shortcuts"><span class="secno">7.4 </span>Assigning keyboard shortcuts</h3><h4 id="introduction-5"><span class="secno">7.4.1 </span>Introduction</h4><p>Each element that can be activated or focused can be assigned a
   single key combination to activate it, using the <code title="attr-accesskey"><a href="#the-accesskey-attribute" id="accesskey_1">accesskey</a></code> attribute.<p>The exact shortcut is determined by the user agent, based on
   information about the user's keyboard, what keyboard shortcuts
   already exist on the platform, and what other shortcuts have been

Index: video.html
===================================================================
RCS file: /sources/public/html5/spec-author-view/video.html,v
retrieving revision 1.993
retrieving revision 1.994
diff -u -d -r1.993 -r1.994
--- video.html	22 Apr 2011 19:54:37 -0000	1.993
+++ video.html	23 Apr 2011 01:54:18 -0000	1.994
@@ -1834,7 +1834,7 @@
 
    </dd>
 
-  </dl><h5 id="mediaevents"><span class="secno">4.8.10.13 </span>Event summary</h5><p><i>This section is non-normative.</i><p>The following events fire on <a href="#media-element" id="media-element_32" title="media element">media
+  </dl><h5 id="mediaevents"><span class="secno">4.8.10.13 </span>Event summary</h5><p>The following events fire on <a href="#media-element" id="media-element_32" title="media element">media
   elements</a> as part of the processing model described above:<table><thead><tr><th>Event name
      <th>Interface
      <th>Dispatched when...
@@ -1935,7 +1935,7 @@
      <td><code><a class="full-spec-link" href="http://dev.w3.org/html5/spec/infrastructure.html#event" title='Read about this "Event" reference in the full HTML5 spec.'>Event</a></code>
      <td>Either the <code title="dom-media-volume"><a class="full-spec-link" href="http://dev.w3.org/html5/spec/video.html#dom-media-volume" title='Read about this "volume" reference in the full HTML5 spec.'>volume</a></code> attribute or the <code title="dom-media-muted"><a class="full-spec-link" href="http://dev.w3.org/html5/spec/video.html#dom-media-muted" title='Read about this "muted" reference in the full HTML5 spec.'>muted</a></code> attribute has changed. Fired after the relevant attribute's setter has returned.
      <td>
-  </table><h5 id="best-practices-for-authors-using-media-elements"><span class="secno">4.8.10.14 </span>Best practices for authors using media elements</h5><p><i>This section is non-normative.</i><p>Playing audio and video resources on small devices such as
+  </table><h5 id="best-practices-for-authors-using-media-elements"><span class="secno">4.8.10.14 </span>Best practices for authors using media elements</h5><p>Playing audio and video resources on small devices such as
   set-top boxes or mobile phones is often constrained by limited
   hardware resources in the device. For example, a device might only
   support three simultaneous videos. For this reason, it is a good

Index: edits.html
===================================================================
RCS file: /sources/public/html5/spec-author-view/edits.html,v
retrieving revision 1.411
retrieving revision 1.412
diff -u -d -r1.411 -r1.412
--- edits.html	22 Apr 2011 19:54:28 -0000	1.411
+++ edits.html	23 Apr 2011 01:54:14 -0000	1.412
@@ -459,7 +459,7 @@
   interface:<pre class="idl">interface <dfn id="htmlmodelement">HTMLModElement</dfn> : <a href="elements.html#htmlelement" id="htmlelement_65">HTMLElement</a> {
            attribute DOMString <a class="full-spec-link" href="http://dev.w3.org/html5/spec/edits.html#dom-mod-cite" title='Read about this "cite" reference in the full HTML5 spec.'>cite</a>;
            attribute DOMString <a class="full-spec-link" href="http://dev.w3.org/html5/spec/edits.html#dom-mod-datetime" title='Read about this "dateTime" reference in the full HTML5 spec.'>dateTime</a>;
-};</pre><h4 id="edits-and-paragraphs"><span class="secno">4.7.4 </span>Edits and paragraphs</h4><p><i>This section is non-normative.</i><p>Since the <code><a href="#the-ins-element" id="ins_17">ins</a></code> and <code><a href="#the-del-element" id="del_17">del</a></code> elements do not
+};</pre><h4 id="edits-and-paragraphs"><span class="secno">4.7.4 </span>Edits and paragraphs</h4><p>Since the <code><a href="#the-ins-element" id="ins_17">ins</a></code> and <code><a href="#the-del-element" id="del_17">del</a></code> elements do not
   affect <a href="content-models.html#paragraph" id="paragraph_12" title="paragraph">paragraphing</a>, it is possible,
   in some cases where paragraphs are <a href="content-models.html#paragraph" id="paragraph_13" title="paragraph">implied</a> (without explicit <code><a href="grouping-content.html#the-p-element" id="p_17">p</a></code>
   elements), for an <code><a href="#the-ins-element" id="ins_18">ins</a></code> or <code><a href="#the-del-element" id="del_18">del</a></code> element to
@@ -499,7 +499,7 @@
   strongly encouraged to always mark up all paragraphs with the
   <code><a href="grouping-content.html#the-p-element" id="p_20">p</a></code> element, instead of having <code><a href="#the-ins-element" id="ins_22">ins</a></code> or
   <code><a href="#the-del-element" id="del_22">del</a></code> elements that cross <a href="content-models.html#paragraph" id="paragraph_15" title="paragraph">implied
-  paragraphs</a> boundaries.<h4 id="edits-and-lists"><span class="secno">4.7.5 </span>Edits and lists</h4><p><i>This section is non-normative.</i><p>The content models of the <code><a href="grouping-content.html#the-ol-element" id="ol_14">ol</a></code> and <code><a href="grouping-content.html#the-ul-element" id="ul_11">ul</a></code>
+  paragraphs</a> boundaries.<h4 id="edits-and-lists"><span class="secno">4.7.5 </span>Edits and lists</h4><p>The content models of the <code><a href="grouping-content.html#the-ol-element" id="ol_14">ol</a></code> and <code><a href="grouping-content.html#the-ul-element" id="ul_11">ul</a></code>
   elements do not allow <code><a href="#the-ins-element" id="ins_23">ins</a></code> and <code><a href="#the-del-element" id="del_23">del</a></code> elements
   as children. Lists always represent all their items, including items
   that would otherwise have been marked as deleted.<p>To indicate that an item is inserted or deleted, an

Index: offline.html
===================================================================
RCS file: /sources/public/html5/spec-author-view/offline.html,v
retrieving revision 1.970
retrieving revision 1.971
diff -u -d -r1.970 -r1.971
--- offline.html	22 Apr 2011 19:54:31 -0000	1.970
+++ offline.html	23 Apr 2011 01:54:15 -0000	1.971
@@ -345,7 +345,7 @@
       <ol><li><a href="offline.html#appcacheevents"><span class="secno">5.6.1.1 </span>Event summary</a></ol><li><a href="offline.html#manifests"><span class="secno">5.6.3 </span>The cache manifest syntax</a>
       <ol><li><a href="offline.html#some-sample-manifests"><span class="secno">5.6.3.1 </span>Some sample manifests</a><li><a href="offline.html#writing-cache-manifests"><span class="secno">5.6.3.2 </span>Writing cache manifests</a></ol><li><a href="offline.html#application-cache-api"><span class="secno">5.6.9 </span>Application cache API</a><li><a href="offline.html#browser-state"><span class="secno">5.6.10 </span>Browser state</a></ol></ol></ol></div>
 
-  <h3 id="offline"><span class="secno">5.6 </span>Offline Web applications</h3><h4 id="introduction-3"><span class="secno">5.6.1 </span>Introduction</h4><p><i>This section is non-normative.</i><p>In order to enable users to continue interacting with Web
+  <h3 id="offline"><span class="secno">5.6 </span>Offline Web applications</h3><h4 id="introduction-3"><span class="secno">5.6.1 </span>Introduction</h4><p>In order to enable users to continue interacting with Web
   applications and documents even when their network connection is
   unavailable &mdash; for instance, because they are traveling outside
   of their ISP's coverage area &mdash; authors can provide a manifest
@@ -394,7 +394,7 @@
   served over TLS (encrypted, using <code title="">https:</code>) are
   overridden by manifests. Thus, pages will not expire from an
   application cache before the user agent has updated it, and even
-  applications served over TLS can be made to work offline.<h5 id="appcacheevents"><span class="secno">5.6.1.1 </span>Event summary</h5><p><i>This section is non-normative.</i><p>When the user visits a page that declares a manifest, the browser
+  applications served over TLS can be made to work offline.<h5 id="appcacheevents"><span class="secno">5.6.1.1 </span>Event summary</h5><p>When the user visits a page that declares a manifest, the browser
   will try to update the cache. It does this by fetching a copy of the
   manifest and, if the manifest has changed since the user agent last
   saw it, redownloading all the resources it mentions and caching them
@@ -441,7 +441,7 @@
     <tr><td> A fatal error occurred while fetching the resources listed in the manifest.
     <tr><td> The manifest changed while the update was being run.
      <td> The user agent will try fetching the files again momentarily.
-  </table><h4 id="manifests"><span class="secno">5.6.2 </span>The cache manifest syntax</h4><h5 id="some-sample-manifests"><span class="secno">5.6.2.1 </span>Some sample manifests</h5><p><i>This section is non-normative.</i><div class="example">
+  </table><h4 id="manifests"><span class="secno">5.6.2 </span>The cache manifest syntax</h4><h5 id="some-sample-manifests"><span class="secno">5.6.2.1 </span>Some sample manifests</h5><div class="example">
 
    <p>This example manifest requires two images and a style sheet to be
    cached and whitelists a CGI script.</p>

--- NEW FILE: full-spec.html ---
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
<html lang="en-US-x-Hixie"><head><meta http-equiv="Content-Type" content="text/html; charset=ascii"><title>HTML5 (Edition for Web Authors)</title>
<meta name="viewport" content="width=device-width;">
<meta content="IE=edge,chrome=1" http-equiv="X-UA-Compatible">
<link href="whatwg.css" rel="stylesheet">
<style type="text/css">
   pre { margin-left: 2em; white-space: pre-wrap; }
   h2 { margin: 3em 0 1em 0; }
   h3 { margin: 2.5em 0 1em 0; }
   h4 { margin: 2.5em 0 0.75em 0; }
   h5, h6 { margin: 2.5em 0 1em; }
   h1 + h2, h1 + h2 + h2 { margin: 0.75em 0 0.75em; }
   h2 + h3, h3 + h4, h4 + h5, h5 + h6 { margin-top: 0.5em; }
   p { margin: 1em 0; }
   hr:not(.top) { display: block; background: none; border: none; padding: 0; margin: 2em 0; height: auto; }
   dl, dd { margin-top: 0; margin-bottom: 0; }
   dt { margin-top: 0.75em; margin-bottom: 0.25em; clear: left; }
   dt + dt { margin-top: 0; }
   dd dt { margin-top: 0.25em; margin-bottom: 0; }
[...70193 lines suppressed...]
  lists</a> and the <a href="http://www.whatwg.org/mailing-list">various WHATWG lists</a>.

  </p><p>Special thanks to Richard Williamson for creating the first
  implementation of <code><a href="#the-canvas-element">canvas</a></code> in Safari, from which the
  canvas feature was designed.</p><p>Special thanks also to the Microsoft employees who first
  implemented the event-based drag-and-drop mechanism, <code title="attr-contenteditable"><a href="#attr-contenteditable">contenteditable</a></code>, and other
  features first widely deployed by the Windows Internet Explorer
  browser.</p><div class="impl">

  <p>Special thanks and $10,000 to David Hyatt who came up with a
  broken implementation of the <a href="#adoptionAgency">adoption
  agency algorithm</a> that the editor had to reverse engineer and fix
  before using it in the parsing section.</p>

  </div><p>Thanks to the many sources that provided inspiration for the
  examples used in the specification.</p><p>Thanks also to the Microsoft blogging community for some ideas,
  to the attendees of the W3C Workshop on Web Applications and
  Compound Documents for inspiration, to the #mrt crew, the #mrt.no
  crew, and the #whatwg crew, and to Pillar and Hedral for their ideas
  and support.</p></body></html>

Index: index.html
===================================================================
RCS file: /sources/public/html5/spec-author-view/index.html,v
retrieving revision 1.985
retrieving revision 1.986
diff -u -d -r1.985 -r1.986
--- index.html	22 Apr 2011 19:54:29 -0000	1.985
+++ index.html	23 Apr 2011 01:54:15 -0000	1.986
@@ -343,7 +343,7 @@
   <ol class="toc"><li><ol><li><ol><li><ol><li><a href="index.html#multipart-form-data"><span class="secno">4.10.22.6 </span>Multipart form data</a></ol></ol></ol><li><a class="no-num" href="index.html#index">Index</a>
   <ol><li><a class="no-num" href="index.html#elements-1">Elements</a><li><a class="no-num" href="index.html#element-content-categories">Element content categories</a><li><a class="no-num" href="index.html#attributes-1">Attributes</a><li><a class="no-num" href="index.html#interfaces">Interfaces</a><li><a class="no-num" href="index.html#events-0">Events</a></ol></ol></div>
 
-  <h2 class="no-num" id="index">Index</h2><h3 class="no-num" id="elements-1">Elements</h3><p><i>This section is non-normative.</i><table><caption>List of elements</caption>
+  <h2 class="no-num" id="index">Index</h2><h3 class="no-num" id="elements-1">Elements</h3><table><caption>List of elements</caption>
    <thead><tr><th> Element
      <th> Description
      <th> Categories
@@ -1483,7 +1483,7 @@
      <td>empty</td>
      <td><a href="elements.html#global-attributes" id="global-attributes_205" title="global attributes">globals</a></td>
      <td><code><a href="elements.html#htmlelement" id="htmlelement_150">HTMLElement</a></code></td>
-    </table><p>An asterisk (*) in a cell indicates that the actual rules are more complicated than indicated in the table above.<h3 class="no-num" id="element-content-categories">Element content categories</h3><p><i>This section is non-normative.</i><table><caption>List of element content categories</caption>
+    </table><p>An asterisk (*) in a cell indicates that the actual rules are more complicated than indicated in the table above.<h3 class="no-num" id="element-content-categories">Element content categories</h3><table><caption>List of element content categories</caption>
    <thead><tr><th> Category
      <th> Elements
      <th> Elements with exceptions
@@ -1793,7 +1793,7 @@
      <td>
       &mdash;
 
-  </table><h3 class="no-num" id="attributes-1">Attributes</h3><p><i>This section is non-normative.</i><table><caption>List of attributes (excluding event handler content attributes)</caption>
+  </table><h3 class="no-num" id="attributes-1">Attributes</h3><table><caption>List of attributes (excluding event handler content attributes)</caption>
    <thead><tr><th> Attribute
      <th> Element(s)
      <th> Description
@@ -2817,7 +2817,7 @@
      <td> <code title="event-media-waiting"><a href="video.html#event-media-waiting" id="waiting">waiting</a></code> event handler
      <td> <a href="webappapis.html#event-handler-content-attributes" id="event-handler-content-attributes_81" title="event handler content attributes">Event handler content attribute</a>
 
-  </table><h3 class="no-num" id="interfaces">Interfaces</h3><p><i>This section is non-normative.</i><table><caption>List of interfaces for elements</caption>
+  </table><h3 class="no-num" id="interfaces">Interfaces</h3><table><caption>List of interfaces for elements</caption>
    <thead><tr><th> Element(s)
      <th> Interface(s)
    <tbody><tr><td> <code><a href="text-level-semantics.html#the-a-element" id="a_76">a</a></code>
@@ -3132,7 +3132,7 @@
     <tr><td> <code><a href="text-level-semantics.html#the-wbr-element" id="wbr_8">wbr</a></code>
      <td> <code><a href="elements.html#htmlelement" id="htmlelement_254">HTMLElement</a></code>
 
-  </table><h3 class="no-num" id="events-0">Events</h3><p><i>This section is non-normative.</i><table><caption>List of events</caption>
+  </table><h3 class="no-num" id="events-0">Events</h3><table><caption>List of events</caption>
    <thead><tr><th> Event
      <th> Interface
      <th> Description

Index: dnd.html
===================================================================
RCS file: /sources/public/html5/spec-author-view/dnd.html,v
retrieving revision 1.419
retrieving revision 1.420
diff -u -d -r1.419 -r1.420
--- dnd.html	22 Apr 2011 19:54:28 -0000	1.419
+++ dnd.html	23 Apr 2011 01:54:14 -0000	1.420
@@ -351,7 +351,7 @@
   the drop could be triggered by the mouse being released.<p>On media without a pointing device, the user would probably have
   to explicitly indicate his intention to perform a drag-and-drop
   operation, stating what he wishes to drag and where he wishes to
-  drop it, respectively.<h4 id="introduction-6"><span class="secno">7.7.1 </span>Introduction</h4><p><i>This section is non-normative.</i><p>To make an element draggable is simple: give the element a <code title="attr-draggable"><a href="#the-draggable-attribute" id="draggable_0">draggable</a></code> attribute, and set an event
+  drop it, respectively.<h4 id="introduction-6"><span class="secno">7.7.1 </span>Introduction</h4><p>To make an element draggable is simple: give the element a <code title="attr-draggable"><a href="#the-draggable-attribute" id="draggable_0">draggable</a></code> attribute, and set an event
   listener for <code title="event-dragstart"><a href="#event-dragstart" id="dragstart">dragstart</a></code> that
   stores the data being dragged.<p>The event handler typically needs to check that it's not a text
   selection that is being dragged, and then needs to store data into
@@ -771,7 +771,7 @@
 
    </dd>
 
-  </dl><h4 id="dndevents"><span class="secno">7.7.5 </span>Events summary</h4><p><i>This section is non-normative.</i><p>The following events are involved in the drag-and-drop
+  </dl><h4 id="dndevents"><span class="secno">7.7.5 </span>Events summary</h4><p>The following events are involved in the drag-and-drop
   model.<table><thead><tr><th> Event Name </th>
      <th> Target </th>
      

Index: spec.html
===================================================================
RCS file: /sources/public/html5/spec-author-view/spec.html,v
retrieving revision 1.1381
retrieving revision 1.1382
diff -u -d -r1.1381 -r1.1382
--- spec.html	22 Apr 2011 19:54:31 -0000	1.1381
+++ spec.html	23 Apr 2011 01:54:15 -0000	1.1382
@@ -1051,14 +1051,14 @@
 <li><a class="no-num" href="#index-of-terms">Index of terms</a></li>
 <li><a class="no-num" href="#references">References</a></li>
 
- <li><a class="no-num" href="#acknowledgements">Acknowledgements</a></li></ol><hr><h2 id="introduction"><span class="secno">1 </span>Introduction</h2><h3 id="background"><span class="secno">1.1 </span>Background</h3><p><i>This section is non-normative.</i></p><p>The World Wide Web's markup language has always been HTML. HTML
+ <li><a class="no-num" href="#acknowledgements">Acknowledgements</a></li></ol><hr><h2 id="introduction"><span class="secno">1 </span>Introduction</h2><h3 id="background"><span class="secno">1.1 </span>Background</h3><p>The World Wide Web's markup language has always been HTML. HTML
   was primarily designed as a language for semantically describing
   scientific documents, although its general design and adaptations
   over the years have enabled it to be used to describe a number of
   other types of documents.</p><p>The main area that has not been adequately addressed by HTML is a
   vague subject referred to as Web Applications. This specification
   attempts to rectify this, while at the same time updating the HTML
-  specifications to address issues raised in the past few years.</p><h3 id="audience"><span class="secno">1.2 </span>Audience</h3><p><i>This section is non-normative.</i></p><p>This specification is intended for authors of documents and
+  specifications to address issues raised in the past few years.</p><h3 id="audience"><span class="secno">1.2 </span>Audience</h3><p>This specification is intended for authors of documents and
   scripts that use the features defined in this specification.</p><p>This document is probably not suited to readers who do not
   already have at least a passing familiarity with Web technologies,
   as in places it sacrifices clarity for precision, and brevity for
@@ -1067,7 +1067,7 @@
   Events is necessary for a complete understanding of some of the more
   technical parts of this specification. An understanding of Web IDL,
   HTTP, XML, Unicode, character encodings, JavaScript, and CSS will
-  also be helpful in places but is not essential.</p><h3 id="scope"><span class="secno">1.3 </span>Scope</h3><p><i>This section is non-normative.</i></p><p>This specification is limited to providing a semantic-level
+  also be helpful in places but is not essential.</p><h3 id="scope"><span class="secno">1.3 </span>Scope</h3><p>This specification is limited to providing a semantic-level
   markup language and associated semantic-level scripting APIs for
   authoring accessible pages on the Web ranging from static documents
   to dynamic applications.</p><p>The scope of this specification does not include providing
@@ -1085,7 +1085,7 @@
   systems, searching systems, games (especially multiplayer online
   games), public telephone books or address books, communications
   software (e-mail clients, instant messaging clients, discussion
-  software), document editing software, etc.</p><h3 id="history-1"><span class="secno">1.4 </span>History</h3><p><i>This section is non-normative.</i></p><p>For its first five years (1990-1995), HTML went through a number
+  software), document editing software, etc.</p><h3 id="history-1"><span class="secno">1.4 </span>History</h3><p>For its first five years (1990-1995), HTML went through a number
   of revisions and experienced a number of extensions, primarily
   hosted first at CERN, and then at the IETF.</p><p>With the creation of the W3C, HTML's development changed venue
   again. A first abortive attempt at extending HTML in 1995 known as
@@ -1157,7 +1157,7 @@
   minor differences. For an exact list of differences, please see the
   WHATWG specification.</p><p>A separate document has been published by the W3C HTML working
   group to document the differences between this specification and the
-  language described in the HTML4 specification. <a href="#refsHTMLDIFF">[HTMLDIFF]</a></p><h3 id="design-notes"><span class="secno">1.5 </span>Design notes</h3><p><i>This section is non-normative.</i></p><p>It must be admitted that many aspects of HTML appear at first
+  language described in the HTML4 specification. <a href="#refsHTMLDIFF">[HTMLDIFF]</a></p><h3 id="design-notes"><span class="secno">1.5 </span>Design notes</h3><p>It must be admitted that many aspects of HTML appear at first
   glance to be nonsensical and inconsistent.</p><p>HTML, its supporting DOM APIs, as well as many of its supporting
   technologies, have been developed over a period of several decades
   by a wide array of people with different priorities who, in many
@@ -1167,20 +1167,20 @@
   often become de-facto, and now de-jure, standards, as content is
   often unintentionally written in ways that rely on them before they
   can be fixed.</p><p>Despite all this, efforts have been made to adhere to certain
-  design goals. These are described in the next few subsections.</p><h4 id="serializability-of-script-execution"><span class="secno">1.5.1 </span>Serializability of script execution</h4><p><i>This section is non-normative.</i></p><p>To avoid exposing Web authors to the complexities of
+  design goals. These are described in the next few subsections.</p><h4 id="serializability-of-script-execution"><span class="secno">1.5.1 </span>Serializability of script execution</h4><p>To avoid exposing Web authors to the complexities of
   multithreading, the HTML and DOM APIs are designed such that no
   script can ever detect the simultaneous execution of other
   scripts. Even with <span title="Worker">workers</span>, the intent
   is that the behavior of implementations can be thought of as
   completely serializing the execution of all scripts in all <a href="#browsing-context" id="browsing-context_0" title="browsing context">browsing contexts</a>.</p><p class="note">The <code title="dom-navigator-yieldForStorageUpdates"><a href="http://dev.w3.org/html5/spec/timers.html#dom-navigator-yieldforstorageupdates" class="full-spec-link" title='Read about this "navigator.yieldForStorageUpdates()" reference in the full HTML5 spec.'>navigator.yieldForStorageUpdates()</a></code>
   method, in this model, is equivalent to allowing other scripts to
-  run while the calling script is blocked.</p><h4 id="compliance-with-other-specifications"><span class="secno">1.5.2 </span>Compliance with other specifications</h4><p><i>This section is non-normative.</i></p><p>This specification interacts with and relies on a wide variety of
+  run while the calling script is blocked.</p><h4 id="compliance-with-other-specifications"><span class="secno">1.5.2 </span>Compliance with other specifications</h4><p>This specification interacts with and relies on a wide variety of
   other specifications. In certain circumstances, unfortunately,
   conflicting needs have led to this specification violating the
   requirements of these other specifications. Whenever this has
   occurred, the transgressions have each been noted as a "<dfn id="willful-violation">willful
   violation</dfn>", and the reason for the violation has been
-  noted.</p><h3 id="html-vs-xhtml"><span class="secno">1.6 </span>HTML vs XHTML</h3><p><i>This section is non-normative.</i></p><p>This specification defines an abstract language for describing
+  noted.</p><h3 id="html-vs-xhtml"><span class="secno">1.6 </span>HTML vs XHTML</h3><p>This specification defines an abstract language for describing
   documents and applications, and some APIs for interacting with
   in-memory representations of resources that use this language.</p><p>The in-memory representation is known as "DOM HTML", or "the DOM"
   for short. This specification defines version 5 of DOM HTML, known
@@ -1215,7 +1215,7 @@
   Similarly, documents that use the <code><a href="#the-noscript-element" id="noscript">noscript</a></code> feature can
   be represented using the HTML syntax, but cannot be represented with
   the DOM or in XML. Comments that contain the string "<code title="">--&gt;</code>" can only be represented in the DOM, not in
-  the HTML and XML syntaxes.</p><h3 id="structure-of-this-specification"><span class="secno">1.7 </span>Structure of this specification</h3><p><i>This section is non-normative.</i></p><p>This specification is divided into the following major
+  the HTML and XML syntaxes.</p><h3 id="structure-of-this-specification"><span class="secno">1.7 </span>Structure of this specification</h3><p>This specification is divided into the following major
   sections:</p><dl><dt><a href="#infrastructure">Common infrastructure</a></dt>
 
    <dd>The conformance classes, algorithms, definitions, and the
@@ -1286,7 +1286,7 @@
   <a href="#x-this" id="x-this_0" title="x-this">this</a> or like <i title="x-this"><a href="#x-this" id="this">this</a></i>.</p><p>The defining instance of an element, attribute, or API is marked
   up like <dfn id="x-that" title="x-that"><code>this</code></dfn>. References to
   that element, attribute, or API are marked up like <code title="x-that"><a href="#x-that" id="this_0">this</a></code>.</p><p>Other code fragments are marked up <code title="">like
-  this</code>.</p><p>Variables are marked up like <var title="">this</var>.</p><h3 id="a-quick-introduction-to-html"><span class="secno">1.8 </span>A quick introduction to HTML</h3><p><i>This section is non-normative.</i></p><p>A basic HTML document looks like this:</p><pre id="intro-early-example">&lt;!DOCTYPE html&gt;
+  this</code>.</p><p>Variables are marked up like <var title="">this</var>.</p><h3 id="a-quick-introduction-to-html"><span class="secno">1.8 </span>A quick introduction to HTML</h3><p>A basic HTML document looks like this:</p><pre id="intro-early-example">&lt;!DOCTYPE html&gt;
 &lt;html&gt;
  &lt;head&gt;
   &lt;title&gt;Sample page&lt;/title&gt;
@@ -1379,7 +1379,7 @@
   specification might also be of use, but the novice author is
   cautioned that this specification, by necessity, defines the
   language with a level of detail that might be difficult to
-  understand at first.</p><h3 id="conformance-requirements-for-authors"><span class="secno">1.9 </span>Conformance requirements for authors</h3><p><i>This section is non-normative.</i></p><p>Unlike previous versions of the HTML specification, this
+  understand at first.</p><h3 id="conformance-requirements-for-authors"><span class="secno">1.9 </span>Conformance requirements for authors</h3><p>Unlike previous versions of the HTML specification, this
   specification defines in some detail the required processing for
   invalid documents as well as valid documents.</p><p>However, even though the processing of invalid content is in most
   cases well-defined, conformance requirements for documents are still
@@ -1388,7 +1388,7 @@
   identical or equivalent way) is not the only goal of document
   conformance requirements. This section details some of the more
   common reasons for still distinguishing between a conforming
-  document and one with errors.</p><h4 id="presentational-markup"><span class="secno">1.9.1 </span>Presentational markup</h4><p><i>This section is non-normative.</i></p><p>The majority of presentational features from previous versions of
+  document and one with errors.</p><h4 id="presentational-markup"><span class="secno">1.9.1 </span>Presentational markup</h4><p>The majority of presentational features from previous versions of
   HTML are no longer allowed. Presentational markup in general has
   been found to have a number of problems:</p><dl><dt>The use of presentational elements leads to poorer accessibility</dt>
 
@@ -1450,7 +1450,7 @@
   pages.</p><p>It is also worth noting that some elements that were previously
   presentational have been redefined in this specification to be
   media-independent: <code><a href="#the-b-element" id="b">b</a></code>, <code><a href="#the-i-element" id="i">i</a></code>, <code><a href="#the-hr-element" id="hr">hr</a></code>,
-  <code><a href="#the-s-element" id="s">s</a></code>, <code><a href="#the-small-element" id="small">small</a></code>, and <code><a href="#the-u-element" id="u">u</a></code>.</p><h4 id="syntax-errors"><span class="secno">1.9.2 </span>Syntax errors</h4><p><i>This section is non-normative.</i></p><p>The syntax of HTML is constrained to avoid a wide variety of
+  <code><a href="#the-s-element" id="s">s</a></code>, <code><a href="#the-small-element" id="small">small</a></code>, and <code><a href="#the-u-element" id="u">u</a></code>.</p><h4 id="syntax-errors"><span class="secno">1.9.2 </span>Syntax errors</h4><p>The syntax of HTML is constrained to avoid a wide variety of
   problems.</p><dl><dt>Unintuitive error-handling behavior</dt>
 
    <dd>
@@ -1696,7 +1696,7 @@
   benefits of terseness afforded by making use of the flexibility of
   the HTML syntax. To aid such authors, conformance checkers can
   provide modes of operation wherein such conventions are
-  enforced.</p><h4 id="restrictions-on-content-models-and-on-attribute-values"><span class="secno">1.9.3 </span>Restrictions on content models and on attribute values</h4><p><i>This section is non-normative.</i></p><p>Beyond the syntax of the language, this specification also places
+  enforced.</p><h4 id="restrictions-on-content-models-and-on-attribute-values"><span class="secno">1.9.3 </span>Restrictions on content models and on attribute values</h4><p>Beyond the syntax of the language, this specification also places
   restrictions on how elements and attributes can be specified. These
   restrictions are present for similar reasons:</p><dl><dt>Errors involving content with dubious semantics</dt>
 
@@ -1934,7 +1934,7 @@
 
    </dd>
 
-  </dl><h3 id="recommended-reading"><span class="secno">1.10 </span>Recommended reading</h3><p><i>This section is non-normative.</i></p><p>The following documents might be of interest to readers of this
+  </dl><h3 id="recommended-reading"><span class="secno">1.10 </span>Recommended reading</h3><p>The following documents might be of interest to readers of this
   specification.</p><dl><dt><cite>Character Model for the World Wide Web 1.0: Fundamentals</cite> <a href="#refsCHARMOD">[CHARMOD]</a></dt>
 
    <dd><blockquote><p>This Architectural Specification provides
@@ -9998,7 +9998,7 @@
    <pre>&lt;p&gt;So then he pointed at the tiger and screamed
 "there&lt;wbr&gt;is&lt;wbr&gt;no&lt;wbr&gt;way&lt;wbr&gt;you&lt;wbr&gt;are&lt;wbr&gt;ever&lt;wbr&gt;going&lt;wbr&gt;to&lt;wbr&gt;catch&lt;wbr&gt;me"!&lt;/p&gt;</pre>
 
-  </div><h4 id="usage-summary"><span class="secno">4.6.28 </span>Usage summary</h4><p><i>This section is non-normative.</i></p><table><thead><tr><th>Element
+  </div><h4 id="usage-summary"><span class="secno">4.6.28 </span>Usage summary</h4><table><thead><tr><th>Element
      </th><th>Purpose
      </th><th>Example
    </th></tr></thead><tbody><tr><td><code><a href="#the-a-element" id="a_19">a</a></code>
@@ -10221,7 +10221,7 @@
   interface:</p><pre class="idl">interface <dfn id="htmlmodelement">HTMLModElement</dfn> : <a href="#htmlelement" id="htmlelement_65">HTMLElement</a> {
            attribute DOMString <a href="http://dev.w3.org/html5/spec/edits.html#dom-mod-cite" title='Read about this "cite" reference in the full HTML5 spec.' class="full-spec-link">cite</a>;
            attribute DOMString <a href="http://dev.w3.org/html5/spec/edits.html#dom-mod-datetime" title='Read about this "dateTime" reference in the full HTML5 spec.' class="full-spec-link">dateTime</a>;
-};</pre><h4 id="edits-and-paragraphs"><span class="secno">4.7.4 </span>Edits and paragraphs</h4><p><i>This section is non-normative.</i></p><p>Since the <code><a href="#the-ins-element" id="ins_17">ins</a></code> and <code><a href="#the-del-element" id="del_17">del</a></code> elements do not
+};</pre><h4 id="edits-and-paragraphs"><span class="secno">4.7.4 </span>Edits and paragraphs</h4><p>Since the <code><a href="#the-ins-element" id="ins_17">ins</a></code> and <code><a href="#the-del-element" id="del_17">del</a></code> elements do not
   affect <a href="#paragraph" id="paragraph_12" title="paragraph">paragraphing</a>, it is possible,
   in some cases where paragraphs are <a href="#paragraph" id="paragraph_13" title="paragraph">implied</a> (without explicit <code><a href="#the-p-element" id="p_17">p</a></code>
   elements), for an <code><a href="#the-ins-element" id="ins_18">ins</a></code> or <code><a href="#the-del-element" id="del_18">del</a></code> element to
@@ -10261,7 +10261,7 @@
   strongly encouraged to always mark up all paragraphs with the
   <code><a href="#the-p-element" id="p_20">p</a></code> element, instead of having <code><a href="#the-ins-element" id="ins_22">ins</a></code> or
   <code><a href="#the-del-element" id="del_22">del</a></code> elements that cross <a href="#paragraph" id="paragraph_15" title="paragraph">implied
-  paragraphs</a> boundaries.</p><h4 id="edits-and-lists"><span class="secno">4.7.5 </span>Edits and lists</h4><p><i>This section is non-normative.</i></p><p>The content models of the <code><a href="#the-ol-element" id="ol_14">ol</a></code> and <code><a href="#the-ul-element" id="ul_11">ul</a></code>
+  paragraphs</a> boundaries.</p><h4 id="edits-and-lists"><span class="secno">4.7.5 </span>Edits and lists</h4><p>The content models of the <code><a href="#the-ol-element" id="ol_14">ol</a></code> and <code><a href="#the-ul-element" id="ul_11">ul</a></code>
   elements do not allow <code><a href="#the-ins-element" id="ins_23">ins</a></code> and <code><a href="#the-del-element" id="del_23">del</a></code> elements
   as children. Lists always represent all their items, including items
   that would otherwise have been marked as deleted.</p><p>To indicate that an item is inserted or deleted, an
@@ -13157,7 +13157,7 @@
 
    </dd>
 
-  </dl><h5 id="mediaevents"><span class="secno">4.8.10.13 </span>Event summary</h5><p><i>This section is non-normative.</i></p><p>The following events fire on <a href="#media-element" id="media-element_32" title="media element">media
+  </dl><h5 id="mediaevents"><span class="secno">4.8.10.13 </span>Event summary</h5><p>The following events fire on <a href="#media-element" id="media-element_32" title="media element">media
   elements</a> as part of the processing model described above:</p><table><thead><tr><th>Event name
      </th><th>Interface
      </th><th>Dispatched when...
@@ -13258,7 +13258,7 @@
      </td><td><code><a href="http://dev.w3.org/html5/spec/infrastructure.html#event" class="full-spec-link" title='Read about this "Event" reference in the full HTML5 spec.'>Event</a></code>
      </td><td>Either the <code title="dom-media-volume"><a href="http://dev.w3.org/html5/spec/video.html#dom-media-volume" class="full-spec-link" title='Read about this "volume" reference in the full HTML5 spec.'>volume</a></code> attribute or the <code title="dom-media-muted"><a href="http://dev.w3.org/html5/spec/video.html#dom-media-muted" class="full-spec-link" title='Read about this "muted" reference in the full HTML5 spec.'>muted</a></code> attribute has changed. Fired after the relevant attribute's setter has returned.
      </td><td>
-  </td></tr></tbody></table><h5 id="best-practices-for-authors-using-media-elements"><span class="secno">4.8.10.14 </span>Best practices for authors using media elements</h5><p><i>This section is non-normative.</i></p><p>Playing audio and video resources on small devices such as
+  </td></tr></tbody></table><h5 id="best-practices-for-authors-using-media-elements"><span class="secno">4.8.10.14 </span>Best practices for authors using media elements</h5><p>Playing audio and video resources on small devices such as
   set-top boxes or mobile phones is often constrained by limited
   hardware resources in the device. For example, a device might only
   support three simultaneous videos. For this reason, it is a good
@@ -13531,13 +13531,13 @@
      </th><th>Keywords
      </th></tr></thead><tbody><tr><td rowspan="2"><a href="#attr-area-shape-circle" id="attr-area-shape-circle_0" title="attr-area-shape-circle">Circle state</a>
      </td><td><dfn id="attr-area-shape-keyword-circle" title="attr-area-shape-keyword-circle"><code>circle</code></dfn>
-     </td></tr><tr><td><a href="#attr-area-shape-default" id="attr-area-shape-default_0" title="attr-area-shape-default">Default state</a>
+     </td></tr><tr></tr><tr><td><a href="#attr-area-shape-default" id="attr-area-shape-default_0" title="attr-area-shape-default">Default state</a>
      </td><td><dfn id="attr-area-shape-keyword-default" title="attr-area-shape-keyword-default"><code>default</code></dfn>
      </td></tr><tr><td rowspan="2"><a href="#attr-area-shape-poly" id="attr-area-shape-poly_0" title="attr-area-shape-poly">Polygon state</a>
      </td><td><dfn id="attr-area-shape-keyword-poly" title="attr-area-shape-keyword-poly"><code>poly</code></dfn>
-     </td></tr><tr><td rowspan="2"><a href="#attr-area-shape-rect" id="attr-area-shape-rect_0" title="attr-area-shape-rect">Rectangle state</a>
+     </td></tr><tr></tr><tr><td rowspan="2"><a href="#attr-area-shape-rect" id="attr-area-shape-rect_0" title="attr-area-shape-rect">Rectangle state</a>
      </td><td><dfn id="attr-area-shape-keyword-rect" title="attr-area-shape-keyword-rect"><code>rect</code></dfn>
-     </td></tr></tbody></table><p>The attribute may be omitted. The <i>missing value default</i> is
+     </td></tr><tr></tr></tbody></table><p>The attribute may be omitted. The <i>missing value default</i> is
   the <a href="#attr-area-shape-rect" id="attr-area-shape-rect_1" title="attr-area-shape-rect">rectangle</a> state.</p><p>The <dfn id="attr-area-coords" title="attr-area-coords"><code>coords</code></dfn>
   attribute must, if specified, contain a <a href="#valid-list-of-integers" id="valid-list-of-integers_0">valid list of
   integers</a>. This attribute gives the coordinates for the shape
@@ -14511,7 +14511,7 @@
 
    </dd>
 
-  </dl><h4 id="examples"><span class="secno">4.9.12 </span>Examples</h4><p><i>This section is non-normative.</i></p><p>The following shows how might one mark up the bottom part of
+  </dl><h4 id="examples"><span class="secno">4.9.12 </span>Examples</h4><p>The following shows how might one mark up the bottom part of
   table 45 of the <cite>Smithsonian physical tables, Volume
   71</cite>:</p><pre>&lt;table&gt;
  &lt;caption&gt;Specification values: &lt;b&gt;Steel&lt;/b&gt;, &lt;b&gt;Castings&lt;/b&gt;,
@@ -14638,7 +14638,7 @@
          </th><td> $ 3,761 </td><td> $ 2,963 </td><td> $ 2,433
     </td></tr><tr><th scope="row"> Percentage of net sales
          </th><td> 11.6% </td><td> 12.3% </td><td> 12.6%
-  </td></tr></tbody></table><h3 id="forms"><span class="secno">4.10 </span>Forms</h3><h4 id="introduction-0"><span class="secno">4.10.1 </span>Introduction</h4><p><i>This section is non-normative.</i></p><p>A form is a component of a Web page that has form controls, such
+  </td></tr></tbody></table><h3 id="forms"><span class="secno">4.10 </span>Forms</h3><h4 id="introduction-0"><span class="secno">4.10.1 </span>Introduction</h4><p>A form is a component of a Web page that has form controls, such
   as text fields, buttons, checkboxes, range controls, or color
   pickers. A user can interact with such a form, providing data that
   can then be sent to the server for further processing (e.g.
@@ -14648,7 +14648,7 @@
   purposes other than submitting data to a server.</p><p>Writing a form consists of several steps, which can be performed
   in any order: writing the user interface, implementing the
   server-side processing, and configuring the user interface to
-  communicate with the server.</p><h5 id="writing-a-form-s-user-interface"><span class="secno">4.10.1.1 </span>Writing a form's user interface</h5><p><i>This section is non-normative.</i></p><p>For the purposes of this brief introduction, we will create a
+  communicate with the server.</p><h5 id="writing-a-form-s-user-interface"><span class="secno">4.10.1.1 </span>Writing a form's user interface</h5><p>For the purposes of this brief introduction, we will create a
   pizza ordering form.</p><p>Any form starts with a <code><a href="#the-form-element" id="form_12">form</a></code> element, inside which
   are placed the controls. Most controls are represented by the
   <code><a href="#the-input-element" id="input_46">input</a></code> element, which by default provides a one-line
@@ -14782,7 +14782,7 @@
  &lt;p&gt;&lt;label&gt;Preferred delivery time: &lt;input type=time min="11:00" max="21:00" step="900"&gt;&lt;/label&gt;&lt;/p&gt;
  &lt;p&gt;&lt;label&gt;Delivery instructions: &lt;textarea&gt;&lt;/textarea&gt;&lt;/label&gt;&lt;/p&gt;
 <strong> &lt;p&gt;&lt;button&gt;Submit order&lt;/button&gt;&lt;/p&gt;</strong>
-&lt;/form&gt;</pre><h5 id="implementing-the-server-side-processing-for-a-form"><span class="secno">4.10.1.2 </span>Implementing the server-side processing for a form</h5><p><i>This section is non-normative.</i></p><p>The exact details for writing a server-side processor are out of
+&lt;/form&gt;</pre><h5 id="implementing-the-server-side-processing-for-a-form"><span class="secno">4.10.1.2 </span>Implementing the server-side processing for a form</h5><p>The exact details for writing a server-side processor are out of
   scope for this specification. For the purposes of this introduction,
   we will assume that the script at <code title="">https://pizza.example.com/order.cgi</code> is configured to
   accept submissions using the <code title="attr-fs-enctype-urlencoded"><a href="#attr-fs-enctype-urlencoded" id="application-x-www-form-urlencoded">application/x-www-form-urlencoded</a></code>
@@ -14808,7 +14808,7 @@
    <dt><code title="">comments</code></dt>
    <dd>The delivery instructions</dd>
 
-  </dl><h5 id="configuring-a-form-to-communicate-with-a-server"><span class="secno">4.10.1.3 </span>Configuring a form to communicate with a server</h5><p><i>This section is non-normative.</i></p><p>Form submissions are exposed to servers in a variety of ways,
+  </dl><h5 id="configuring-a-form-to-communicate-with-a-server"><span class="secno">4.10.1.3 </span>Configuring a form to communicate with a server</h5><p>Form submissions are exposed to servers in a variety of ways,
   most commonly as HTTP GET or POST requests. To specify the exact
   method used, the <code title="attr-fs-method"><a href="#attr-fs-method" id="method">method</a></code>
   attribute is specified on the <code><a href="#the-form-element" id="form_13">form</a></code> element. This
@@ -14853,7 +14853,7 @@
   e-mail address, asked for a medium-sized pizza, selected the Extra
   Cheese and Mushroom toppings, entered a delivery time of 7pm, and
   left the delivery instructions text field blank, the user agent
-  would submit the following to the online Web service:</p><pre>custname=Denise+Lawrence&amp;custtel=555-321-8624&amp;custemail=&amp;size=medium&amp;topping=cheese&amp;topping=mushroom&amp;delivery=19%3A00&amp;comments=</pre><h5 id="client-side-form-validation"><span class="secno">4.10.1.4 </span>Client-side form validation</h5><p><i>This section is non-normative.</i></p><p>Forms can be annotated in such a way that the user agent will
+  would submit the following to the online Web service:</p><pre>custname=Denise+Lawrence&amp;custtel=555-321-8624&amp;custemail=&amp;size=medium&amp;topping=cheese&amp;topping=mushroom&amp;delivery=19%3A00&amp;comments=</pre><h5 id="client-side-form-validation"><span class="secno">4.10.1.4 </span>Client-side form validation</h5><p>Forms can be annotated in such a way that the user agent will
   check the user's input before the form is submitted. The server
   still has to verify the input is valid (since hostile users can
   easily bypass the form validation), but it allows the user to avoid
@@ -19693,7 +19693,7 @@
   hostile users, and unintentionally bypassed by users of older user
   agents or automated tools that do not implement these features. The
   constraint validation features are only intended to improve the user
-  experience, not to provide any kind of security mechanism.</p><h4 id="form-submission"><span class="secno">4.10.22 </span><dfn>Form submission</dfn></h4><p><i>This section is non-normative.</i></p><p>When a form is submitted, the data in the form is converted into
+  experience, not to provide any kind of security mechanism.</p><h4 id="form-submission"><span class="secno">4.10.22 </span><dfn>Form submission</dfn></h4><p>When a form is submitted, the data in the form is converted into
   the structure specified by the <a href="#concept-fs-enctype" id="concept-fs-enctype_1" title="concept-fs-enctype">enctype</a>, and then sent to the
   destination specified by the <a href="#concept-fs-action" id="concept-fs-action_0" title="concept-fs-action">action</a> using the given <a href="#concept-fs-method" id="concept-fs-method_1" title="concept-fs-method">method</a>.</p><p>For example, take the following form:</p><pre>&lt;form action="/find.cgi" method=get&gt;
  &lt;input type=text name=t&gt;
@@ -19939,7 +19939,7 @@
   attribute gives the label of the menu. It is used by user agents to
   display nested menus in the UI. For example, a context menu
   containing another menu would use the nested menu's <code title="attr-menu-label"><a href="#attr-menu-label" id="label_40">label</a></code> attribute for the submenu's
-  menu label.</p><h5 id="menus-intro"><span class="secno">4.11.4.1 </span>Introduction</h5><p><i>This section is non-normative.</i></p><p>The <code><a href="#menus" id="menu_17">menu</a></code> element is used to define context menus and
+  menu label.</p><h5 id="menus-intro"><span class="secno">4.11.4.1 </span>Introduction</h5><p>The <code><a href="#menus" id="menu_17">menu</a></code> element is used to define context menus and
   toolbars.</p><p>For example, the following represents a toolbar with three menu
   buttons on it, each of which has a dropdown menu with a series of
   options:</p><pre>&lt;menu type="toolbar"&gt;
@@ -21882,7 +21882,7 @@
    </dd>
 
   </dl><p class="note">There are no <code><a href="#beforeunloadevent" id="beforeunloadevent_0">BeforeUnloadEvent</a></code>-specific
-  initialization methods.</p><h3 id="offline"><span class="secno">5.6 </span>Offline Web applications</h3><h4 id="introduction-3"><span class="secno">5.6.1 </span>Introduction</h4><p><i>This section is non-normative.</i></p><p>In order to enable users to continue interacting with Web
+  initialization methods.</p><h3 id="offline"><span class="secno">5.6 </span>Offline Web applications</h3><h4 id="introduction-3"><span class="secno">5.6.1 </span>Introduction</h4><p>In order to enable users to continue interacting with Web
   applications and documents even when their network connection is
   unavailable — for instance, because they are traveling outside
   of their ISP's coverage area — authors can provide a manifest
@@ -21931,7 +21931,7 @@
   served over TLS (encrypted, using <code title="">https:</code>) are
   overridden by manifests. Thus, pages will not expire from an
   application cache before the user agent has updated it, and even
-  applications served over TLS can be made to work offline.</p><h5 id="appcacheevents"><span class="secno">5.6.1.1 </span>Event summary</h5><p><i>This section is non-normative.</i></p><p>When the user visits a page that declares a manifest, the browser
+  applications served over TLS can be made to work offline.</p><h5 id="appcacheevents"><span class="secno">5.6.1.1 </span>Event summary</h5><p>When the user visits a page that declares a manifest, the browser
   will try to update the cache. It does this by fetching a copy of the
   manifest and, if the manifest has changed since the user agent last
   saw it, redownloading all the resources it mentions and caching them
@@ -21978,7 +21978,7 @@
     </td></tr><tr><td> A fatal error occurred while fetching the resources listed in the manifest.
     </td></tr><tr><td> The manifest changed while the update was being run.
      </td><td> The user agent will try fetching the files again momentarily.
-  </td></tr></tbody></table><h4 id="manifests"><span class="secno">5.6.2 </span>The cache manifest syntax</h4><h5 id="some-sample-manifests"><span class="secno">5.6.2.1 </span>Some sample manifests</h5><p><i>This section is non-normative.</i></p><div class="example">
+  </td></tr></tbody></table><h4 id="manifests"><span class="secno">5.6.2 </span>The cache manifest syntax</h4><h5 id="some-sample-manifests"><span class="secno">5.6.2.1 </span>Some sample manifests</h5><div class="example">
 
    <p>This example manifest requires two images and a style sheet to be
    cached and whitelists a CGI script.</p>
@@ -22819,7 +22819,7 @@
 
    </dd>
 
-  </dl><h3 id="assigning-keyboard-shortcuts"><span class="secno">7.4 </span>Assigning keyboard shortcuts</h3><h4 id="introduction-5"><span class="secno">7.4.1 </span>Introduction</h4><p><i>This section is non-normative.</i></p><p>Each element that can be activated or focused can be assigned a
+  </dl><h3 id="assigning-keyboard-shortcuts"><span class="secno">7.4 </span>Assigning keyboard shortcuts</h3><h4 id="introduction-5"><span class="secno">7.4.1 </span>Introduction</h4><p>Each element that can be activated or focused can be assigned a
   single key combination to activate it, using the <code title="attr-accesskey"><a href="#the-accesskey-attribute" id="accesskey_1">accesskey</a></code> attribute.</p><p>The exact shortcut is determined by the user agent, based on
   information about the user's keyboard, what keyboard shortcuts
   already exist on the platform, and what other shortcuts have been
@@ -22964,7 +22964,7 @@
   the drop could be triggered by the mouse being released.</p><p>On media without a pointing device, the user would probably have
   to explicitly indicate his intention to perform a drag-and-drop
   operation, stating what he wishes to drag and where he wishes to
-  drop it, respectively.</p><h4 id="introduction-6"><span class="secno">7.7.1 </span>Introduction</h4><p><i>This section is non-normative.</i></p><p>To make an element draggable is simple: give the element a <code title="attr-draggable"><a href="#the-draggable-attribute" id="draggable_0">draggable</a></code> attribute, and set an event
+  drop it, respectively.</p><h4 id="introduction-6"><span class="secno">7.7.1 </span>Introduction</h4><p>To make an element draggable is simple: give the element a <code title="attr-draggable"><a href="#the-draggable-attribute" id="draggable_0">draggable</a></code> attribute, and set an event
   listener for <code title="event-dragstart"><a href="#event-dragstart" id="dragstart">dragstart</a></code> that
   stores the data being dragged.</p><p>The event handler typically needs to check that it's not a text
   selection that is being dragged, and then needs to store data into
@@ -23384,7 +23384,7 @@
 
    </dd>
 
-  </dl><h4 id="dndevents"><span class="secno">7.7.5 </span>Events summary</h4><p><i>This section is non-normative.</i></p><p>The following events are involved in the drag-and-drop
+  </dl><h4 id="dndevents"><span class="secno">7.7.5 </span>Events summary</h4><p>The following events are involved in the drag-and-drop
   model.</p><table><thead><tr><th> Event Name </th>
      <th> Target </th>
      
@@ -25009,7 +25009,7 @@
    <dt>Change controller:</dt>
    <dd>W3C</dd>
   </dl><p>Fragment identifiers have no meaning with
-  <code><a href="#text-cache-manifest" id="text-cache-manifest_3">text/cache-manifest</a></code> resources.</p><h2 class="no-num" id="index">Index</h2><h3 class="no-num" id="elements-1">Elements</h3><p><i>This section is non-normative.</i></p><table><caption>List of elements</caption>
+  <code><a href="#text-cache-manifest" id="text-cache-manifest_3">text/cache-manifest</a></code> resources.</p><h2 class="no-num" id="index">Index</h2><h3 class="no-num" id="elements-1">Elements</h3><table><caption>List of elements</caption>
    <thead><tr><th> Element
      </th><th> Description
      </th><th> Categories
@@ -26149,7 +26149,7 @@
      <td>empty</td>
      <td><a href="#global-attributes" id="global-attributes_205" title="global attributes">globals</a></td>
      <td><code><a href="#htmlelement" id="htmlelement_150">HTMLElement</a></code></td>
-    </tr></tbody></table><p>An asterisk (*) in a cell indicates that the actual rules are more complicated than indicated in the table above.</p><h3 class="no-num" id="element-content-categories">Element content categories</h3><p><i>This section is non-normative.</i></p><table><caption>List of element content categories</caption>
+    </tr></tbody></table><p>An asterisk (*) in a cell indicates that the actual rules are more complicated than indicated in the table above.</p><h3 class="no-num" id="element-content-categories">Element content categories</h3><table><caption>List of element content categories</caption>
    <thead><tr><th> Category
      </th><th> Elements
      </th><th> Elements with exceptions
@@ -26459,7 +26459,7 @@
      </td><td>
       —
 
-  </td></tr></tbody></table><h3 class="no-num" id="attributes-1">Attributes</h3><p><i>This section is non-normative.</i></p><table><caption>List of attributes (excluding event handler content attributes)</caption>
+  </td></tr></tbody></table><h3 class="no-num" id="attributes-1">Attributes</h3><table><caption>List of attributes (excluding event handler content attributes)</caption>
    <thead><tr><th> Attribute
      </th><th> Element(s)
      </th><th> Description
@@ -27483,7 +27483,7 @@
      </td><td> <code title="event-media-waiting"><a href="#event-media-waiting" id="waiting">waiting</a></code> event handler
      </td><td> <a href="#event-handler-content-attributes" id="event-handler-content-attributes_81" title="event handler content attributes">Event handler content attribute</a>
 
-  </td></tr></tbody></table><h3 class="no-num" id="interfaces">Interfaces</h3><p><i>This section is non-normative.</i></p><table><caption>List of interfaces for elements</caption>
+  </td></tr></tbody></table><h3 class="no-num" id="interfaces">Interfaces</h3><table><caption>List of interfaces for elements</caption>
    <thead><tr><th> Element(s)
      </th><th> Interface(s)
    </th></tr></thead><tbody><tr><td> <code><a href="#the-a-element" id="a_76">a</a></code>
@@ -27798,7 +27798,7 @@
     </td></tr><tr><td> <code><a href="#the-wbr-element" id="wbr_8">wbr</a></code>
      </td><td> <code><a href="#htmlelement" id="htmlelement_254">HTMLElement</a></code>
 
-  </td></tr></tbody></table><h3 class="no-num" id="events-0">Events</h3><p><i>This section is non-normative.</i></p><table><caption>List of events</caption>
+  </td></tr></tbody></table><h3 class="no-num" id="events-0">Events</h3><table><caption>List of events</caption>
    <thead><tr><th> Event
      </th><th> Interface
      </th><th> Description

Index: Makefile
===================================================================
RCS file: /sources/public/html5/spec-author-view/Makefile,v
retrieving revision 1.46
retrieving revision 1.47
diff -u -d -r1.46 -r1.47
--- Makefile	22 Apr 2011 10:55:47 -0000	1.46
+++ Makefile	23 Apr 2011 01:54:14 -0000	1.47
@@ -42,12 +42,15 @@
 #	  --filter=.impl \
 #	  --output-encoding="ascii" \
 #	  $< $@.tmp
+	cp $< full-spec.html
+	$(PERL) $(PERLFLAGS) -pi -e "s/<td class='impl'>/<td>-<span class='impl'>/" full-spec.html
+	$(PERL) $(PERLFLAGS) -pi -e "s/<th class='impl'>/<th>-<span class='impl'>/" full-spec.html
 	$(PYTHON) anolis/anolis \
 	  --parser=lxml.html \
 	  --enable terms \
 	  --filter=.impl \
 	  --output-encoding="ascii" \
-	  $< $@.tmp
+	  full-spec.html $@.tmp
 	$(XSLTPROC) $(XSLTPROCFLAGS) \
 	  --html \
 	  tools/postprocess.xsl \
@@ -84,6 +87,7 @@
 	touch $@
 
 clean:
+	$(RM) full-spec.html
 	$(RM) spec.preprocessed.html
 	$(RM) spec.html.tmp
 	$(RM) spec.html

Index: introduction.html
===================================================================
RCS file: /sources/public/html5/spec-author-view/introduction.html,v
retrieving revision 1.977
retrieving revision 1.978
diff -u -d -r1.977 -r1.978
--- introduction.html	22 Apr 2011 19:54:30 -0000	1.977
+++ introduction.html	23 Apr 2011 01:54:15 -0000	1.978
@@ -344,14 +344,14 @@
     <ol><li><a href="introduction.html#how-to-read-this-specification"><span class="secno">1.7.1 </span>How to read this specification</a><li><a href="introduction.html#typographic-conventions"><span class="secno">1.7.2 </span>Typographic conventions</a></ol><li><a href="introduction.html#a-quick-introduction-to-html"><span class="secno">1.8 </span>A quick introduction to HTML</a><li><a href="introduction.html#conformance-requirements-for-authors"><span class="secno">1.9 </span>Conformance requirements for authors</a>
     <ol><li><a href="introduction.html#presentational-markup"><span class="secno">1.9.1 </span>Presentational markup</a><li><a href="introduction.html#syntax-errors"><span class="secno">1.9.2 </span>Syntax errors</a><li><a href="introduction.html#restrictions-on-content-models-and-on-attribute-values"><span class="secno">1.9.3 </span>Restrictions on content models and on attribute values</a></ol><li><a href="introduction.html#recommended-reading"><span class="secno">1.10 </span>Recommended reading</a></ol></ol></div>
 
-  <h2 id="introduction"><span class="secno">1 </span>Introduction</h2><h3 id="background"><span class="secno">1.1 </span>Background</h3><p><i>This section is non-normative.</i><p>The World Wide Web's markup language has always been HTML. HTML
+  <h2 id="introduction"><span class="secno">1 </span>Introduction</h2><h3 id="background"><span class="secno">1.1 </span>Background</h3><p>The World Wide Web's markup language has always been HTML. HTML
   was primarily designed as a language for semantically describing
   scientific documents, although its general design and adaptations
   over the years have enabled it to be used to describe a number of
   other types of documents.<p>The main area that has not been adequately addressed by HTML is a
   vague subject referred to as Web Applications. This specification
   attempts to rectify this, while at the same time updating the HTML
-  specifications to address issues raised in the past few years.<h3 id="audience"><span class="secno">1.2 </span>Audience</h3><p><i>This section is non-normative.</i><p>This specification is intended for authors of documents and
+  specifications to address issues raised in the past few years.<h3 id="audience"><span class="secno">1.2 </span>Audience</h3><p>This specification is intended for authors of documents and
   scripts that use the features defined in this specification.<p>This document is probably not suited to readers who do not
   already have at least a passing familiarity with Web technologies,
   as in places it sacrifices clarity for precision, and brevity for
@@ -360,7 +360,7 @@
   Events is necessary for a complete understanding of some of the more
   technical parts of this specification. An understanding of Web IDL,
   HTTP, XML, Unicode, character encodings, JavaScript, and CSS will
-  also be helpful in places but is not essential.<h3 id="scope"><span class="secno">1.3 </span>Scope</h3><p><i>This section is non-normative.</i><p>This specification is limited to providing a semantic-level
+  also be helpful in places but is not essential.<h3 id="scope"><span class="secno">1.3 </span>Scope</h3><p>This specification is limited to providing a semantic-level
   markup language and associated semantic-level scripting APIs for
   authoring accessible pages on the Web ranging from static documents
   to dynamic applications.<p>The scope of this specification does not include providing
@@ -378,7 +378,7 @@
   systems, searching systems, games (especially multiplayer online
   games), public telephone books or address books, communications
   software (e-mail clients, instant messaging clients, discussion
-  software), document editing software, etc.<h3 id="history-1"><span class="secno">1.4 </span>History</h3><p><i>This section is non-normative.</i><p>For its first five years (1990-1995), HTML went through a number
+  software), document editing software, etc.<h3 id="history-1"><span class="secno">1.4 </span>History</h3><p>For its first five years (1990-1995), HTML went through a number
   of revisions and experienced a number of extensions, primarily
   hosted first at CERN, and then at the IETF.<p>With the creation of the W3C, HTML's development changed venue
   again. A first abortive attempt at extending HTML in 1995 known as
@@ -450,7 +450,7 @@
   minor differences. For an exact list of differences, please see the
   WHATWG specification.<p>A separate document has been published by the W3C HTML working
   group to document the differences between this specification and the
-  language described in the HTML4 specification. <a href="references.html#refsHTMLDIFF">[HTMLDIFF]</a><h3 id="design-notes"><span class="secno">1.5 </span>Design notes</h3><p><i>This section is non-normative.</i><p>It must be admitted that many aspects of HTML appear at first
+  language described in the HTML4 specification. <a href="references.html#refsHTMLDIFF">[HTMLDIFF]</a><h3 id="design-notes"><span class="secno">1.5 </span>Design notes</h3><p>It must be admitted that many aspects of HTML appear at first
   glance to be nonsensical and inconsistent.<p>HTML, its supporting DOM APIs, as well as many of its supporting
   technologies, have been developed over a period of several decades
   by a wide array of people with different priorities who, in many
@@ -460,20 +460,20 @@
   often become de-facto, and now de-jure, standards, as content is
   often unintentionally written in ways that rely on them before they
   can be fixed.<p>Despite all this, efforts have been made to adhere to certain
-  design goals. These are described in the next few subsections.<h4 id="serializability-of-script-execution"><span class="secno">1.5.1 </span>Serializability of script execution</h4><p><i>This section is non-normative.</i><p>To avoid exposing Web authors to the complexities of
+  design goals. These are described in the next few subsections.<h4 id="serializability-of-script-execution"><span class="secno">1.5.1 </span>Serializability of script execution</h4><p>To avoid exposing Web authors to the complexities of
   multithreading, the HTML and DOM APIs are designed such that no
   script can ever detect the simultaneous execution of other
   scripts. Even with <span title="Worker">workers</span>, the intent
   is that the behavior of implementations can be thought of as
   completely serializing the execution of all scripts in all <a href="browsers.html#browsing-context" id="browsing-context_0" title="browsing context">browsing contexts</a>.<p class="note">The <code title="dom-navigator-yieldForStorageUpdates"><a class="full-spec-link" href="http://dev.w3.org/html5/spec/timers.html#dom-navigator-yieldforstorageupdates" title='Read about this "navigator.yieldForStorageUpdates()" reference in the full HTML5 spec.'>navigator.yieldForStorageUpdates()</a></code>
   method, in this model, is equivalent to allowing other scripts to
-  run while the calling script is blocked.<h4 id="compliance-with-other-specifications"><span class="secno">1.5.2 </span>Compliance with other specifications</h4><p><i>This section is non-normative.</i><p>This specification interacts with and relies on a wide variety of
+  run while the calling script is blocked.<h4 id="compliance-with-other-specifications"><span class="secno">1.5.2 </span>Compliance with other specifications</h4><p>This specification interacts with and relies on a wide variety of
   other specifications. In certain circumstances, unfortunately,
   conflicting needs have led to this specification violating the
   requirements of these other specifications. Whenever this has
   occurred, the transgressions have each been noted as a "<dfn id="willful-violation">willful
   violation</dfn>", and the reason for the violation has been
-  noted.<h3 id="html-vs-xhtml"><span class="secno">1.6 </span>HTML vs XHTML</h3><p><i>This section is non-normative.</i><p>This specification defines an abstract language for describing
+  noted.<h3 id="html-vs-xhtml"><span class="secno">1.6 </span>HTML vs XHTML</h3><p>This specification defines an abstract language for describing
   documents and applications, and some APIs for interacting with
   in-memory representations of resources that use this language.<p>The in-memory representation is known as "DOM HTML", or "the DOM"
   for short. This specification defines version 5 of DOM HTML, known
@@ -508,7 +508,7 @@
   Similarly, documents that use the <code><a href="scripting-1.html#the-noscript-element" id="noscript">noscript</a></code> feature can
   be represented using the HTML syntax, but cannot be represented with
   the DOM or in XML. Comments that contain the string "<code title="">--&gt;</code>" can only be represented in the DOM, not in
-  the HTML and XML syntaxes.<h3 id="structure-of-this-specification"><span class="secno">1.7 </span>Structure of this specification</h3><p><i>This section is non-normative.</i><p>This specification is divided into the following major
+  the HTML and XML syntaxes.<h3 id="structure-of-this-specification"><span class="secno">1.7 </span>Structure of this specification</h3><p>This specification is divided into the following major
   sections:<dl><dt><a href="infrastructure.html#infrastructure">Common infrastructure</a></dt>
 
    <dd>The conformance classes, algorithms, definitions, and the
@@ -579,7 +579,7 @@
   <a href="#x-this" id="x-this_0" title="x-this">this</a> or like <i title="x-this"><a href="#x-this" id="this">this</a></i>.<p>The defining instance of an element, attribute, or API is marked
   up like <dfn id="x-that" title="x-that"><code>this</code></dfn>. References to
   that element, attribute, or API are marked up like <code title="x-that"><a href="#x-that" id="this_0">this</a></code>.<p>Other code fragments are marked up <code title="">like
-  this</code>.<p>Variables are marked up like <var title="">this</var>.<h3 id="a-quick-introduction-to-html"><span class="secno">1.8 </span>A quick introduction to HTML</h3><p><i>This section is non-normative.</i><p>A basic HTML document looks like this:<pre id="intro-early-example">&lt;!DOCTYPE html&gt;
+  this</code>.<p>Variables are marked up like <var title="">this</var>.<h3 id="a-quick-introduction-to-html"><span class="secno">1.8 </span>A quick introduction to HTML</h3><p>A basic HTML document looks like this:<pre id="intro-early-example">&lt;!DOCTYPE html&gt;
 &lt;html&gt;
  &lt;head&gt;
   &lt;title&gt;Sample page&lt;/title&gt;
@@ -672,7 +672,7 @@
   specification might also be of use, but the novice author is
   cautioned that this specification, by necessity, defines the
   language with a level of detail that might be difficult to
-  understand at first.<h3 id="conformance-requirements-for-authors"><span class="secno">1.9 </span>Conformance requirements for authors</h3><p><i>This section is non-normative.</i><p>Unlike previous versions of the HTML specification, this
+  understand at first.<h3 id="conformance-requirements-for-authors"><span class="secno">1.9 </span>Conformance requirements for authors</h3><p>Unlike previous versions of the HTML specification, this
   specification defines in some detail the required processing for
   invalid documents as well as valid documents.<p>However, even though the processing of invalid content is in most
   cases well-defined, conformance requirements for documents are still
@@ -681,7 +681,7 @@
   identical or equivalent way) is not the only goal of document
   conformance requirements. This section details some of the more
   common reasons for still distinguishing between a conforming
-  document and one with errors.<h4 id="presentational-markup"><span class="secno">1.9.1 </span>Presentational markup</h4><p><i>This section is non-normative.</i><p>The majority of presentational features from previous versions of
+  document and one with errors.<h4 id="presentational-markup"><span class="secno">1.9.1 </span>Presentational markup</h4><p>The majority of presentational features from previous versions of
   HTML are no longer allowed. Presentational markup in general has
   been found to have a number of problems:<dl><dt>The use of presentational elements leads to poorer accessibility</dt>
 
@@ -743,7 +743,7 @@
   pages.<p>It is also worth noting that some elements that were previously
   presentational have been redefined in this specification to be
   media-independent: <code><a href="text-level-semantics.html#the-b-element" id="b">b</a></code>, <code><a href="text-level-semantics.html#the-i-element" id="i">i</a></code>, <code><a href="grouping-content.html#the-hr-element" id="hr">hr</a></code>,
-  <code><a href="text-level-semantics.html#the-s-element" id="s">s</a></code>, <code><a href="text-level-semantics.html#the-small-element" id="small">small</a></code>, and <code><a href="text-level-semantics.html#the-u-element" id="u">u</a></code>.<h4 id="syntax-errors"><span class="secno">1.9.2 </span>Syntax errors</h4><p><i>This section is non-normative.</i><p>The syntax of HTML is constrained to avoid a wide variety of
+  <code><a href="text-level-semantics.html#the-s-element" id="s">s</a></code>, <code><a href="text-level-semantics.html#the-small-element" id="small">small</a></code>, and <code><a href="text-level-semantics.html#the-u-element" id="u">u</a></code>.<h4 id="syntax-errors"><span class="secno">1.9.2 </span>Syntax errors</h4><p>The syntax of HTML is constrained to avoid a wide variety of
   problems.<dl><dt>Unintuitive error-handling behavior</dt>
 
    <dd>
@@ -989,7 +989,7 @@
   benefits of terseness afforded by making use of the flexibility of
   the HTML syntax. To aid such authors, conformance checkers can
   provide modes of operation wherein such conventions are
-  enforced.<h4 id="restrictions-on-content-models-and-on-attribute-values"><span class="secno">1.9.3 </span>Restrictions on content models and on attribute values</h4><p><i>This section is non-normative.</i><p>Beyond the syntax of the language, this specification also places
+  enforced.<h4 id="restrictions-on-content-models-and-on-attribute-values"><span class="secno">1.9.3 </span>Restrictions on content models and on attribute values</h4><p>Beyond the syntax of the language, this specification also places
   restrictions on how elements and attributes can be specified. These
   restrictions are present for similar reasons:<dl><dt>Errors involving content with dubious semantics</dt>
 
@@ -1227,7 +1227,7 @@
 
    </dd>
 
-  </dl><h3 id="recommended-reading"><span class="secno">1.10 </span>Recommended reading</h3><p><i>This section is non-normative.</i><p>The following documents might be of interest to readers of this
+  </dl><h3 id="recommended-reading"><span class="secno">1.10 </span>Recommended reading</h3><p>The following documents might be of interest to readers of this
   specification.<dl><dt><cite>Character Model for the World Wide Web 1.0: Fundamentals</cite> <a href="references.html#refsCHARMOD">[CHARMOD]</a></dt>
 
    <dd><blockquote><p>This Architectural Specification provides
Received on Saturday, 23 April 2011 01:54:26 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 23 April 2011 01:56:42 GMT