hixie: add notes and fix typos (whatwg r3443)

hixie: add notes and fix typos (whatwg r3443)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.2567&r2=1.2568&f=h
http://html5.org/tools/web-apps-tracker?from=3442&to=3443

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.2567
retrieving revision 1.2568
diff -u -d -r1.2567 -r1.2568
--- Overview.html 17 Jul 2009 11:42:21 -0000 1.2567
+++ Overview.html 18 Jul 2009 00:45:50 -0000 1.2568
@@ -175,7 +175,7 @@
    <h2 class="no-num no-toc" id="a-vocabulary-and-associated-apis-for-html-and-xhtml">A vocabulary and associated APIs for HTML and XHTML</h2>
    <!--ZZZ:-->
    <!--<h2 class="no-num no-toc">W3C Working Draft 23 April 2009</h2>-->
-   <h2 class="no-num no-toc" id="editor-s-draft-date-1-january-1970">Editor's Draft 17 July 2009</h2>
+   <h2 class="no-num no-toc" id="editor-s-draft-date-1-january-1970">Editor's Draft 18 July 2009</h2>
    <!--:ZZZ-->
    <dl><!-- ZZZ: update the month/day (twice), (un)comment out
     <dt>This Version:</dt>
@@ -268,7 +268,7 @@
   track.
   <!--ZZZ:-->
   <!--This specification is the 23 April 2009 Working Draft.-->
-  This specification is the 17 July 2009 Editor's Draft.
+  This specification is the 18 July 2009 Editor's Draft.
   <!--:ZZZ-->
   </p><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- relationship to other work (required) --><p>This specification is also being produced by the <a href="http://www.whatwg.org/">WHATWG</a>. The two specifications are
   identical from the table of contents onwards.</p><!-- UNDER NO CIRCUMSTANCES IS THE FOLLOWING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- context and rationale (required) --><p>This specification is intended to replace (be a new version of)
@@ -18263,9 +18263,15 @@
       </ol></dd>
 
 
-     <dt id="getting-media-metadata">Once enough of the <a href="#media-data">media
-     data</a> has been fetched to determine the duration of the
-     <a href="#media-resource">media resource</a>, its dimensions, and other
+     <!-- insert content sniffing here if we want to define that -->
+     <!-- (in practice I don't think that's necessary since it's not
+     like you can do anything with the resource if you sniff it as the
+     wrong type) ->
+
+
+     <dt id="getting-media-metadata">Once enough of the <span>media
+     data</span> has been fetched to determine the duration of the
+     <span>media resource</span>, its dimensions, and other
      metadata</dt>
 
      <dd>
@@ -18273,35 +18279,45 @@
       <p>This indicates that the resource is usable. The user agent
       must follow these substeps:</p>
 
-      <ol><li><p>Set the <a href="#current-playback-position">current playback position</a> to the
-       <a href="#earliest-possible-position">earliest possible position</a>.</li>
+      <ol>
 
-       <li><p>Set the <code title="dom-media-readyState"><a href="#dom-media-readystate">readyState</a></code> attribute to
-       <code title="dom-media-HAVE_METADATA"><a href="#dom-media-have_metadata">HAVE_METADATA</a></code>.</li>
+       <li><p>Set the <span>current playback position</span> to the
+       <span>earliest possible position</span>.</p></li>
 
-       <li><p>For <code><a href="#video">video</a></code> elements, set the <code title="dom-video-videoWidth"><a href="#dom-video-videowidth">videoWidth</a></code> and <code title="dom-video-videoHeight"><a href="#dom-video-videoheight">videoHeight</a></code>
-       attributes.</li>
+       <li><p>Set the <code
+       title="dom-media-readyState">readyState</code> attribute to
+       <code
+       title="dom-media-HAVE_METADATA">HAVE_METADATA</code>.</p></li>
+
+       <li><p>For <code>video</code> elements, set the <code
+       title="dom-video-videoWidth">videoWidth</code> and <code
+       title="dom-video-videoHeight">videoHeight</code>
+       attributes.</p></li>
 
        <li>
 
-        <p>Set the <code title="dom-media-duration"><a href="#dom-media-duration">duration</a></code>
+        <p>Set the <code title="dom-media-duration">duration</code>
         attribute to the duration of the resource.</p>
 
-        <p class="note">The user agent <a href="#durationChange">will</a> <a href="#queue-a-task">queue a task</a> to
-        <a href="#fire-a-simple-event">fire a simple event</a> called <code title="event-durationchange"><a href="#event-durationchange">durationchange</a></code> at the
+        <p class="note">The user agent <a
+        href="#durationChange">will</a> <span>queue a task</span> to
+        <span>fire a simple event</span> called <code
+        title="event-durationchange">durationchange</code> at the
         element at this point.</p>
 
        </li>
 
-       <li id="fire-loadedmetadata"><p><a href="#queue-a-task">Queue a task</a> to
-       <a href="#fire-a-simple-event">fire a simple event</a> called <code title="event-loadedmetadata"><a href="#event-loadedmetadata">loadedmetadata</a></code> at the
+       <li id="fire-loadedmetadata"><p><span>Queue a task</span> to
+       <span>fire a simple event</span> called <code
+       title="event-loadedmetadata">loadedmetadata</code> at the
        element.</li>
 
        <li>
 
-        <p>If either the <a href="#media-resource">media resource</a> or the address
+        <p>If either the <span>media resource</span> or the address
         of the <var title="">current media resource</var> indicate a
-        particular start time, then <a href="#dom-media-seek" title="dom-media-seek">seek</a> to that time. Ignore any
+        particular start time, then <span
+        title="dom-media-seek">seek</span> to that time. Ignore any
         resulting exceptions (if the position is out of range, it is
         effectively ignored).</p>
 
@@ -18312,28 +18328,37 @@
 
        <li>
 
-        <p>Once the <code title="dom-media-readyState"><a href="#dom-media-readystate">readyState</a></code> attribute
-        reaches <code title="dom-media-HAVE_CURRENT_DATA"><a href="#dom-media-have_current_data">HAVE_CURRENT_DATA</a></code>,
-        <a href="#fire-loadeddata">after the <code title="event-loadeddata">loadeddata</code> event has been
-        fired</a>, set the element's <a href="#delaying-the-load-event-flag">delaying-the-load-event
-        flag</a> to false. This stops <a href="#delay-the-load-event" title="delay the load
-        event">delaying the load event</a>.</p>
+        <p>Once the <code
+        title="dom-media-readyState">readyState</code> attribute
+        reaches <code
+        title="dom-media-HAVE_CURRENT_DATA">HAVE_CURRENT_DATA</code>,
+        <a href="#fire-loadeddata">after the <code
+        title="event-loadeddata">loadeddata</code> event has been
+        fired</a>, set the element's <span>delaying-the-load-event
+        flag</span> to false. This stops <span title="delay the load
+        event">delaying the load event</span>.</p>
 
         <p class="note">A user agent that is attempting to reduce
         network usage while still fetching the metadata for each
-        <a href="#media-resource">media resource</a> would also stop buffering at this
-        point, causing the <code title="dom-media-networkState"><a href="#dom-media-networkstate">networkState</a></code> attribute
-        to switch to the <code title="dom-media-NETWORK_IDLE"><a href="#dom-media-network_idle">NETWORK_IDLE</a></code> value, if
-        the <a href="#media-element">media element</a> did not have an <code title="attr-media-autobuffer"><a href="#attr-media-autobuffer">autobuffer</a></code> or <code title="attr-media-autoplay"><a href="#attr-media-autoplay">autoplay</a></code> attribute.</p>
+        <span>media resource</span> would also stop buffering at this
+        point, causing the <code
+        title="dom-media-networkState">networkState</code> attribute
+        to switch to the <code
+        title="dom-media-NETWORK_IDLE">NETWORK_IDLE</code> value, if
+        the <span>media element</span> did not have an <code
+        title="attr-media-autobuffer">autobuffer</code> or <code
+        title="attr-media-autoplay">autoplay</code> attribute.</p>
 
        </li>
 
-      </ol><p class="note">The user agent is <em>required</em> to
-      determine the duration of the <a href="#media-resource">media resource</a> and
+      </ol>
+
+      <p class="note">The user agent is <em>required</em> to
+      determine the duration of the <span>media resource</span> and
       go through this step before playing.</p> <!-- actually defined
       in the 'duration' section -->
 
-     </dd>
+     
 
 
      <dt>If the connection is interrupted, causing the user agent to
@@ -43967,7 +43992,7 @@
   work offline and which causes the user's browser to keep a copy of
   the files for use offline.<p>To illustrate this, consider a simple clock applet consisting of
   an HTML page "<code title="">clock.html</code>", a CSS style sheet
-  "<code title="">clock.css</code>", and a JavaScript script "<code title="">clock.js</code>".<p>Before adding the manifest, three three files might look like
+  "<code title="">clock.css</code>", and a JavaScript script "<code title="">clock.js</code>".<p>Before adding the manifest, these three files might look like
   this:<pre>&lt;!-- clock.html --&gt;
 &lt;!DOCTYPE HTML&gt;
 &lt;html&gt;
@@ -65781,6 +65806,7 @@
   Will Levine,
   William Swanson,
   Wladimir Palant,
+  Wojciech Mach,
   Wolfram Kriesing,
   Yi-An Huang,
   Yngve Nysaeter Pettersen,

Received on Saturday, 18 July 2009 00:48:10 UTC