[html5] r1340 - /

whatwg at whatwg.org whatwg at whatwg.org
Tue Mar 4 12:42:23 PST 2008


Author: ianh
Date: 2008-03-04 12:42:19 -0800 (Tue, 04 Mar 2008)
New Revision: 1340

Modified:
   index
   source
Log:
[e] (0) Fix markup errors in the source.

Modified: index
===================================================================
--- index	2008-03-04 11:55:15 UTC (rev 1339)
+++ index	2008-03-04 20:42:19 UTC (rev 1340)
@@ -8947,20 +8947,20 @@
   <h5 id=outlines><span class=secno>3.8.10.1. </span>Creating an outline</h5>
 
   <p>This section defines an algorithm for creating an <dfn
-   id=outline>outline</dfn> for a <span>sectioning content element or a <a
-   href="#sectioning1">sectioning root</a> element. It is defined in terms of
-   a walk over the nodes of a DOM tree, in tree order, with each node being
-   visited when it is <i>entered</i> and when it is <i>exited</i> during the
-   walk.</span>
+   id=outline>outline</dfn> for a <a href="#sectioning0">sectioning
+   content</a> element or a <a href="#sectioning1">sectioning root</a>
+   element. It is defined in terms of a walk over the nodes of a DOM tree, in
+   tree order, with each node being visited when it is <i>entered</i> and
+   when it is <i>exited</i> during the walk.
 
-  <p>The outline for a <span>sectioning content element or a <a
-   href="#sectioning1">sectioning root</a> element consists of a list of one
-   or more potentially nested sections. Each section can have one heading
-   associated with it. The algorithm for the outline also associates each
-   node in the DOM tree with a particular section and potentially a heading.
-   (The sections in the outline aren't <code><a
+  <p>The outline for a <a href="#sectioning0">sectioning content</a> element
+   or a <a href="#sectioning1">sectioning root</a> element consists of a list
+   of one or more potentially nested sections. Each section can have one
+   heading associated with it. The algorithm for the outline also associates
+   each node in the DOM tree with a particular section and potentially a
+   heading. (The sections in the outline aren't <code><a
    href="#section">section</a></code> elements, though some may correspond to
-   such elements — they are merely conceptual sections.)</span>
+   such elements — they are merely conceptual sections.)
 
   <p>The algorithm that must be followed during a walk of a DOM subtree
    rooted at a <a href="#sectioning0">sectioning content</a> element or a <a
@@ -14958,8 +14958,6 @@
    the <code title=dom-media-start><a href="#start3">start</a></code> DOM
    attribute and the end of the <a href="#media8">media resource</a>.
 
-  <p>
-
   <p>The <dfn id=loopstart
    title=attr-media-loopstart><code>loopstart</code></dfn> content attribute
    gives the offset into the <a href="#media8">media resource</a> at which
@@ -18428,8 +18426,9 @@
    space information in the resource returned. Where the output format allows
    it, the color of pixels in resources created by <code
    title=dom-canvas-toDataURL><a href="#todataurl">toDataURL()</a></code>
-   must match those returned by the code
-   title="dom-context-2d-getImageData">getImageData() method.
+   must match those returned by the <code
+   title=dom-context-2d-getImageData><a
+   href="#getimagedata">getImageData()</a></code> method.
 
   <p>In user agents that support CSS, the color space used by a <code><a
    href="#canvas">canvas</a></code> element must match the color space used
@@ -21339,13 +21338,14 @@
    href="#style">style</a></code>, and <code><a href="#meta0">meta</a></code>
    elements. If <a href="#scripting2">scripting is enabled</a>, then the
    content model of a <code><a href="#noscript">noscript</a></code> element
-   is text, except that invoking the <span>HTML fragment parsing algorithm
-   with the <code><a href="#noscript">noscript</a></code> element as the <var
+   is text, except that invoking the <a href="#html-fragment0">HTML fragment
+   parsing algorithm</a> with the <code><a
+   href="#noscript">noscript</a></code> element as the <var
    title="">context</var> element and the text contents as the <var
    title="">input</var> must result in a list of nodes that consists only of
    <code><a href="#link">link</a></code>, <code><a
    href="#style">style</a></code>, and <code><a href="#meta0">meta</a></code>
-   elements.</span>
+   elements.
 
   <p>Outside of <code><a href="#head">head</a></code> elements, if <a
    href="#scripting1">scripting is disabled</a>, then the content model of a
@@ -28106,15 +28106,15 @@
     <p>If this is an <a href="#upgrade"
      title=concept-appcache-upgrade>upgrade attempt</a>, then add all the
      URIs of <a href="#implicit" title=concept-appcache-implicit>implicit
-     entries in <var title="">cache</var> to <var title="">file list</var>,
-     each flagged with "implicit entry".</a>
+     entries</a> in <var title="">cache</var> to <var title="">file
+     list</var>, each flagged with "implicit entry".
 
    <li>
     <p>If this is an <a href="#upgrade"
      title=concept-appcache-upgrade>upgrade attempt</a>, then add all the
      URIs of <a href="#dynamic3" title=concept-appcache-dynamic>dynamic
-     entries in <var title="">cache</var> to <var title="">file list</var>,
-     each flagged with "dynamic entry".</a>
+     entries</a> in <var title="">cache</var> to <var title="">file
+     list</var>, each flagged with "dynamic entry".
 
    <li>
     <p>If any URI is in <var title="">file list</var> more than once, then
@@ -28998,13 +28998,14 @@
    must act as follows:
 
   <ol>
-   <li>If there is no longer a <code>Document</code> object for the entry in
-    question, the user agent must <a href="#navigate">navigate</a> the
-    browsing context to the location for that entry to preform an <a
-    href="#entry">entry update</a> of that entry, and abort these steps. The
-    "<a href="#navigate">navigate</a>" algorithm reinvokes this "traverse"
-    algorithm to complete the traversal, at which point there <em>is</em> a
-    <code>Document</code> object and so this step gets skipped.
+   <li>
+    <p>If there is no longer a <code>Document</code> object for the entry in
+     question, the user agent must <a href="#navigate">navigate</a> the
+     browsing context to the location for that entry to preform an <a
+     href="#entry">entry update</a> of that entry, and abort these steps. The
+     "<a href="#navigate">navigate</a>" algorithm reinvokes this "traverse"
+     algorithm to complete the traversal, at which point there <em>is</em> a
+     <code>Document</code> object and so this step gets skipped.
 
    <li>
     <p>If appropriate, update the <a href="#current0">current entry</a> in
@@ -29051,8 +29052,8 @@
       the <a href="#active">active document</a> of the <a
       href="#browsing0">browsing context</a>. (If it is a <a
       href="#top-level">top-level browsing context</a>, this might <a
-      href="#appcache-history-1">change which <span>application cache</span>
-      it is associated with.)</a>
+      href="#appcache-history-1">change</a> which <a
+      href="#application0">application cache</a> it is associated with.)
 
      <li>If the <a href="#specified">specified entry</a> has a <a
       href="#browsing1">browsing context name</a> stored with it, then the
@@ -30094,7 +30095,6 @@
    documents about once for every 5000 pages labelled "text/html", and
    "application/unknown" was used about once for every 35000 pages
    labelled "text/html". -->
-    
 
    <li>
     <p>If <var title="">official type</var> ends in "+xml", or if it is
@@ -30177,12 +30177,10 @@
         
     </table>
 
-    <p>...then the sniffed type of the resource is "text/plain".
-  </ol>
+    <p>...then the sniffed type of the resource is "text/plain".</p>
 
-  <p class=big-issue>Should we remove UTF-32 from the above?
+    <p class=big-issue>Should we remove UTF-32 from the above?</p>
 
-  <ul>
    <li>
     <p>Otherwise, if any of the first <var title="">n</var> bytes of the
      resource are in one of the following byte ranges:</p>
@@ -30208,7 +30206,7 @@
 
    <li>
     <p>Otherwise, the sniffed type of the resource is "text/plain".
-  </ul>
+  </ol>
 
   <h4 id=content-type1><span class=secno>4.9.2 </span><dfn
    id=content-type5>Content-Type sniffing: unknown type</dfn></h4>
@@ -36166,8 +36164,8 @@
     the server would be sent a <code title="">Last-Event-ID</code> header
     with the value "1". The third block fires an event with data "second
     event", and also has an "id" field, this time with no value, which resets
-    the last event ID to the empty string (meaning no code
-    title="">Last-Event-ID header will now be sent in the event of a
+    the last event ID to the empty string (meaning no <code
+    title="">Last-Event-ID</code> header will now be sent in the event of a
     reconnection being attempted). Finally the last block just fires an event
     with the data "third event". Note that the last block doesn't have to end
     with a blank line, the end of the stream is enough to trigger the
@@ -37964,7 +37962,7 @@
    ampersand</dfn> is a U+0026 AMPERSAND (<code>&</code>) character that
    is followed by some <a href="#text1" title=syntax-text>text</a> other than
    a <a href="#space">space character</a>, a U+003C LESS-THAN SIGN character
-   ('&lt'), or another U+0026 AMPERSAND (<code>&</code>) character.
+   ('<'), or another U+0026 AMPERSAND (<code>&</code>) character.
 
   <h4 id=comments><span class=secno>8.1.5 </span>Comments</h4>
 
@@ -38254,239 +38252,240 @@
            parse. If an encoding is returned, let <var title="">charset</var>
            be that encoding. Otherwise, return to step 2 in these inner
            steps.
-        </ol>
 
-        <p>If <var title="">charset</var> is a UTF-16 encoding, change it to
-         UTF-8.</p>
+         <li>
+          <p>If <var title="">charset</var> is a UTF-16 encoding, change it
+           to UTF-8.
 
-        <p>If <var title="">charset</var> is a supported character encoding,
-         then return the given encoding, with <a href="#confidence"
-         title=concept-encoding-confidence>confidence</a> <i>tentative</i>,
-         and abort all these steps.</p>
-      </dl>
+         <li>
+          <p>If <var title="">charset</var> is a supported character
+           encoding, then return the given encoding, with <a
+           href="#confidence"
+           title=concept-encoding-confidence>confidence</a> <i>tentative</i>,
+           and abort all these steps.
 
-     <li>
-      <p>Otherwise, return to step 2 in these inner steps.
-    </ol>
+         <li>
+          <p>Otherwise, return to step 2 in these inner steps.
+        </ol>
 
-    <p class=note>Leading and trailing spaces in encoding names are
-     <em>not</em> trimmed, and will result in encodings being treated as
-     unknown.</p>
+        <p class=note>Leading and trailing spaces in encoding names are
+         <em>not</em> trimmed, and will result in encodings being treated as
+         unknown.</p>
 
-    <dl>
-     <dt>A sequence of bytes starting with a 0x3C byte (ASCII '<'),
-      optionally a 0x2F byte (ASCII '/'), and finally a byte in the range
-      0x41-0x5A or 0x61-0x7A (an ASCII letter)
+       <dt>A sequence of bytes starting with a 0x3C byte (ASCII '<'),
+        optionally a 0x2F byte (ASCII '/'), and finally a byte in the range
+        0x41-0x5A or 0x61-0x7A (an ASCII letter)
 
-     <dd>
-      <ol>
-       <li>
-        <p>Advance the <var title="">position</var> pointer so that it points
-         at the next 0x09 (ASCII TAB), 0x0A (ASCII LF), 0x0B (ASCII VT), 0x0C
-         (ASCII FF), 0x0D (ASCII CR), 0x20 (ASCII space), or 0x3E (ASCII '>')
-         byte.
+       <dd>
+        <ol>
+         <li>
+          <p>Advance the <var title="">position</var> pointer so that it
+           points at the next 0x09 (ASCII TAB), 0x0A (ASCII LF), 0x0B (ASCII
+           VT), 0x0C (ASCII FF), 0x0D (ASCII CR), 0x20 (ASCII space), or 0x3E
+           (ASCII '>') byte.
 
-       <li>
-        <p>Repeatedly <a href="#get-an"
-         title=concept-get-attributes-when-sniffing>get an attribute</a>
-         until no further attributes can be found, then jump to the second
-         step in the overall "two step" algorithm.
-      </ol>
+         <li>
+          <p>Repeatedly <a href="#get-an"
+           title=concept-get-attributes-when-sniffing>get an attribute</a>
+           until no further attributes can be found, then jump to the second
+           step in the overall "two step" algorithm.
+        </ol>
 
-     <dt>A sequence of bytes starting with: 0x3C 0x21 (ASCII '<!')
+       <dt>A sequence of bytes starting with: 0x3C 0x21 (ASCII '<!')
 
-     <dt>A sequence of bytes starting with: 0x3C 0x2F (ASCII '</')
+       <dt>A sequence of bytes starting with: 0x3C 0x2F (ASCII '</')
 
-     <dt>A sequence of bytes starting with: 0x3C 0x3F (ASCII '<?')
+       <dt>A sequence of bytes starting with: 0x3C 0x3F (ASCII '<?')
 
-     <dd>
-      <p>Advance the <var title="">position</var> pointer so that it points
-       at the first 0x3E byte (ASCII '>') that comes after the 0x3C byte that
-       was found.</p>
+       <dd>
+        <p>Advance the <var title="">position</var> pointer so that it points
+         at the first 0x3E byte (ASCII '>') that comes after the 0x3C byte
+         that was found.</p>
 
-     <dt>Any other byte
+       <dt>Any other byte
 
-     <dd>
-      <p>Do nothing with that byte.</p>
-    </dl>
+       <dd>
+        <p>Do nothing with that byte.</p>
+      </dl>
 
-   <li>Move <var title="">position</var> so it points at the next byte in the
-    input stream, and return to the first step of this "two step" algorithm.
-  </ol>
+     <li>Move <var title="">position</var> so it points at the next byte in
+      the input stream, and return to the first step of this "two step"
+      algorithm.
+    </ol>
 
-  <p>When the above "two step" algorithm says to <dfn id=get-an
-   title=concept-get-attributes-when-sniffing>get an attribute</dfn>, it
-   means doing this:
+    <p>When the above "two step" algorithm says to <dfn id=get-an
+     title=concept-get-attributes-when-sniffing>get an attribute</dfn>, it
+     means doing this:</p>
 
-  <ol>
-   <li>
-    <p>If the byte at <var title="">position</var> is one of 0x09 (ASCII
-     TAB), 0x0A (ASCII LF), 0x0B (ASCII VT), 0x0C (ASCII FF), 0x0D (ASCII
-     CR), 0x20 (ASCII space), or 0x2F (ASCII '/') then advance <var
-     title="">position</var> to the next byte and redo this substep.
+    <ol>
+     <li>
+      <p>If the byte at <var title="">position</var> is one of 0x09 (ASCII
+       TAB), 0x0A (ASCII LF), 0x0B (ASCII VT), 0x0C (ASCII FF), 0x0D (ASCII
+       CR), 0x20 (ASCII space), or 0x2F (ASCII '/') then advance <var
+       title="">position</var> to the next byte and redo this substep.
 
-   <li>
-    <p>If the byte at <var title="">position</var> is 0x3E (ASCII '>'), then
-     abort the "get an attribute" algorithm. There isn't one.
+     <li>
+      <p>If the byte at <var title="">position</var> is 0x3E (ASCII '>'),
+       then abort the "get an attribute" algorithm. There isn't one.
 
-   <li>
-    <p>Otherwise, the byte at <var title="">position</var> is the start of
-     the attribute name. Let <var title="">attribute name</var> and <var
-     title="">attribute value</var> be the empty string.
+     <li>
+      <p>Otherwise, the byte at <var title="">position</var> is the start of
+       the attribute name. Let <var title="">attribute name</var> and <var
+       title="">attribute value</var> be the empty string.
 
-   <li>
-    <p><em>Attribute name</em>: Process the byte at <var
-     title="">position</var> as follows:</p>
+     <li>
+      <p><em>Attribute name</em>: Process the byte at <var
+       title="">position</var> as follows:</p>
 
-    <dl class=switch>
-     <dt>If it is 0x3D (ASCII '='), and the <var title="">attribute
-      name</var> is longer than the empty string
+      <dl class=switch>
+       <dt>If it is 0x3D (ASCII '='), and the <var title="">attribute
+        name</var> is longer than the empty string
 
-     <dd>Advance <var title="">position</var> to the next byte and jump to
-      the step below labelled <em>value</em>.
+       <dd>Advance <var title="">position</var> to the next byte and jump to
+        the step below labelled <em>value</em>.
 
-     <dt>If it is 0x09 (ASCII TAB), 0x0A (ASCII LF), 0x0B (ASCII VT), 0x0C
-      (ASCII FF), 0x0D (ASCII CR), or 0x20 (ASCII space)
+       <dt>If it is 0x09 (ASCII TAB), 0x0A (ASCII LF), 0x0B (ASCII VT), 0x0C
+        (ASCII FF), 0x0D (ASCII CR), or 0x20 (ASCII space)
 
-     <dd>Jump to the step below labelled <em>spaces</em>.
+       <dd>Jump to the step below labelled <em>spaces</em>.
 
-     <dt>If it is 0x2F (ASCII '/') or 0x3E (ASCII '>')
+       <dt>If it is 0x2F (ASCII '/') or 0x3E (ASCII '>')
 
-     <dd>Abort the "get an attribute" algorithm. The attribute's name is the
-      value of <var title="">attribute name</var>, its value is the empty
-      string.
+       <dd>Abort the "get an attribute" algorithm. The attribute's name is
+        the value of <var title="">attribute name</var>, its value is the
+        empty string.
 
-     <dt>If it is in the range 0x41 (ASCII 'A') to 0x5A (ASCII 'Z')
+       <dt>If it is in the range 0x41 (ASCII 'A') to 0x5A (ASCII 'Z')
 
-     <dd>Append the Unicode character with codepoint <span><var
-      title="">b</var>+0x20</span> to <var title="">attribute name</var>
-      (where <var title="">b</var> is the value of the byte at <var
-      title="">position</var>).
+       <dd>Append the Unicode character with codepoint <span><var
+        title="">b</var>+0x20</span> to <var title="">attribute name</var>
+        (where <var title="">b</var> is the value of the byte at <var
+        title="">position</var>).
 
-     <dt>Anything else
+       <dt>Anything else
 
-     <dd>Append the Unicode character with the same codepoint as the value of
-      the byte at <var title="">position</var>) to <var title="">attribute
-      name</var>. (It doesn't actually matter how bytes outside the ASCII
-      range are handled here, since only ASCII characters can contribute to
-      the detection of a character encoding.)
-    </dl>
+       <dd>Append the Unicode character with the same codepoint as the value
+        of the byte at <var title="">position</var>) to <var
+        title="">attribute name</var>. (It doesn't actually matter how bytes
+        outside the ASCII range are handled here, since only ASCII characters
+        can contribute to the detection of a character encoding.)
+      </dl>
 
-   <li>
-    <p>Advance <var title="">position</var> to the next byte and return to
-     the previous step.
+     <li>
+      <p>Advance <var title="">position</var> to the next byte and return to
+       the previous step.
 
-   <li>
-    <p><em>Spaces.</em> If the byte at <var title="">position</var> is one of
-     0x09 (ASCII TAB), 0x0A (ASCII LF), 0x0B (ASCII VT), 0x0C (ASCII FF),
-     0x0D (ASCII CR), or 0x20 (ASCII space) then advance <var
-     title="">position</var> to the next byte, then, repeat this step.
+     <li>
+      <p><em>Spaces.</em> If the byte at <var title="">position</var> is one
+       of 0x09 (ASCII TAB), 0x0A (ASCII LF), 0x0B (ASCII VT), 0x0C (ASCII
+       FF), 0x0D (ASCII CR), or 0x20 (ASCII space) then advance <var
+       title="">position</var> to the next byte, then, repeat this step.
 
-   <li>
-    <p>If the byte at <var title="">position</var> is <em>not</em> 0x3D
-     (ASCII '='), abort the "get an attribute" algorithm. Move <var
-     title="">position</var> back to the previous byte. The attribute's name
-     is the value of <var title="">attribute name</var>, its value is the
-     empty string.
+     <li>
+      <p>If the byte at <var title="">position</var> is <em>not</em> 0x3D
+       (ASCII '='), abort the "get an attribute" algorithm. Move <var
+       title="">position</var> back to the previous byte. The attribute's
+       name is the value of <var title="">attribute name</var>, its value is
+       the empty string.
 
-   <li>
-    <p>Advance <var title="">position</var> past the 0x3D (ASCII '=') byte.
+     <li>
+      <p>Advance <var title="">position</var> past the 0x3D (ASCII '=') byte.
 
-   <li>
-    <p><em>Value.</em> If the byte at <var title="">position</var> is one of
-     0x09 (ASCII TAB), 0x0A (ASCII LF), 0x0B (ASCII VT), 0x0C (ASCII FF),
-     0x0D (ASCII CR), or 0x20 (ASCII space) then advance <var
-     title="">position</var> to the next byte, then, repeat this step.
+     <li>
+      <p><em>Value.</em> If the byte at <var title="">position</var> is one
+       of 0x09 (ASCII TAB), 0x0A (ASCII LF), 0x0B (ASCII VT), 0x0C (ASCII
+       FF), 0x0D (ASCII CR), or 0x20 (ASCII space) then advance <var
+       title="">position</var> to the next byte, then, repeat this step.
 
-   <li>
-    <p>Process the byte at <var title="">position</var> as follows:</p>
+     <li>
+      <p>Process the byte at <var title="">position</var> as follows:</p>
 
-    <dl class=switch>
-     <dt>If it is 0x22 (ASCII '"') or 0x27 ("'")
+      <dl class=switch>
+       <dt>If it is 0x22 (ASCII '"') or 0x27 ("'")
 
-     <dd>
-      <ol>
-       <li>Let <var title="">b</var> be the value of the byte at <var
-        title="">position</var>.
+       <dd>
+        <ol>
+         <li>Let <var title="">b</var> be the value of the byte at <var
+          title="">position</var>.
 
-       <li>Advance <var title="">position</var> to the next byte.
+         <li>Advance <var title="">position</var> to the next byte.
 
-       <li>If the value of the byte at <var title="">position</var> is the
-        value of <var title="">b</var>, then abort the "get an attribute"
-        algorithm. The attribute's name is the value of <var
-        title="">attribute name</var>, and its value is the value of <var
-        title="">attribute value</var>.
+         <li>If the value of the byte at <var title="">position</var> is the
+          value of <var title="">b</var>, then abort the "get an attribute"
+          algorithm. The attribute's name is the value of <var
+          title="">attribute name</var>, and its value is the value of <var
+          title="">attribute value</var>.
 
-       <li>Otherwise, if the value of the byte at <var
-        title="">position</var> is in the range 0x41 (ASCII 'A') to 0x5A
-        (ASCII 'Z'), then append a Unicode character to <var
-        title="">attribute value</var> whose codepoint is 0x20 more than the
-        value of the byte at <var title="">position</var>.
+         <li>Otherwise, if the value of the byte at <var
+          title="">position</var> is in the range 0x41 (ASCII 'A') to 0x5A
+          (ASCII 'Z'), then append a Unicode character to <var
+          title="">attribute value</var> whose codepoint is 0x20 more than
+          the value of the byte at <var title="">position</var>.
 
-       <li>Otherwise, append a Unicode character to <var title="">attribute
-        value</var> whose codepoint is the same as the value of the byte at
-        <var title="">position</var>.
+         <li>Otherwise, append a Unicode character to <var title="">attribute
+          value</var> whose codepoint is the same as the value of the byte at
+          <var title="">position</var>.
 
-       <li>Return to the second step in these substeps.
-      </ol>
+         <li>Return to the second step in these substeps.
+        </ol>
 
-     <dt>If it is 0x3E (ASCII '>')
+       <dt>If it is 0x3E (ASCII '>')
 
-     <dd>Abort the "get an attribute" algorithm. The attribute's name is the
-      value of <var title="">attribute name</var>, its value is the empty
-      string.
+       <dd>Abort the "get an attribute" algorithm. The attribute's name is
+        the value of <var title="">attribute name</var>, its value is the
+        empty string.
 
-     <dt>If it is in the range 0x41 (ASCII 'A') to 0x5A (ASCII 'Z')
+       <dt>If it is in the range 0x41 (ASCII 'A') to 0x5A (ASCII 'Z')
 
-     <dd>Append the Unicode character with codepoint <span><var
-      title="">b</var>+0x20</span> to <var title="">attribute value</var>
-      (where <var title="">b</var> is the value of the byte at <var
-      title="">position</var>). Advance <var title="">position</var> to the
-      next byte.
+       <dd>Append the Unicode character with codepoint <span><var
+        title="">b</var>+0x20</span> to <var title="">attribute value</var>
+        (where <var title="">b</var> is the value of the byte at <var
+        title="">position</var>). Advance <var title="">position</var> to the
+        next byte.
 
-     <dt>Anything else
+       <dt>Anything else
 
-     <dd>Append the Unicode character with the same codepoint as the value of
-      the byte at <var title="">position</var>) to <var title="">attribute
-      value</var>. Advance <var title="">position</var> to the next byte.
-    </dl>
+       <dd>Append the Unicode character with the same codepoint as the value
+        of the byte at <var title="">position</var>) to <var
+        title="">attribute value</var>. Advance <var title="">position</var>
+        to the next byte.
+      </dl>
 
-   <li>
-    <p>Process the byte at <var title="">position</var> as follows:</p>
+     <li>
+      <p>Process the byte at <var title="">position</var> as follows:</p>
 
-    <dl class=switch>
-     <dt>If it is 0x09 (ASCII TAB), 0x0A (ASCII LF), 0x0B (ASCII VT), 0x0C
-      (ASCII FF), 0x0D (ASCII CR), 0x20 (ASCII space), or 0x3E (ASCII '>')
+      <dl class=switch>
+       <dt>If it is 0x09 (ASCII TAB), 0x0A (ASCII LF), 0x0B (ASCII VT), 0x0C
+        (ASCII FF), 0x0D (ASCII CR), 0x20 (ASCII space), or 0x3E (ASCII '>')
 
-     <dd>Abort the "get an attribute" algorithm. The attribute's name is the
-      value of <var title="">attribute name</var> and its value is the value
-      of <var title="">attribute value</var>.
+       <dd>Abort the "get an attribute" algorithm. The attribute's name is
+        the value of <var title="">attribute name</var> and its value is the
+        value of <var title="">attribute value</var>.
 
-     <dt>If it is in the range 0x41 (ASCII 'A') to 0x5A (ASCII 'Z')
+       <dt>If it is in the range 0x41 (ASCII 'A') to 0x5A (ASCII 'Z')
 
-     <dd>Append the Unicode character with codepoint <span><var
-      title="">b</var>+0x20</span> to <var title="">attribute value</var>
-      (where <var title="">b</var> is the value of the byte at <var
-      title="">position</var>).
+       <dd>Append the Unicode character with codepoint <span><var
+        title="">b</var>+0x20</span> to <var title="">attribute value</var>
+        (where <var title="">b</var> is the value of the byte at <var
+        title="">position</var>).
 
-     <dt>Anything else
+       <dt>Anything else
 
-     <dd>Append the Unicode character with the same codepoint as the value of
-      the byte at <var title="">position</var>) to <var title="">attribute
-      value</var>.
-    </dl>
+       <dd>Append the Unicode character with the same codepoint as the value
+        of the byte at <var title="">position</var>) to <var
+        title="">attribute value</var>.
+      </dl>
 
-   <li>
-    <p>Advance <var title="">position</var> to the next byte and return to
-     the previous step.
-  </ol>
+     <li>
+      <p>Advance <var title="">position</var> to the next byte and return to
+       the previous step.
+    </ol>
 
-  <p>For the sake of interoperability, user agents should not use a pre-scan
-   algorithm that returns different results than the one described above.
-   (But, if you do, please at least let us know, so that we can improve this
-   algorithm and benefit everyone...)
+    <p>For the sake of interoperability, user agents should not use a
+     pre-scan algorithm that returns different results than the one described
+     above. (But, if you do, please at least let us know, so that we can
+     improve this algorithm and benefit everyone...)</p>
 
-  <ul>
    <li>
     <p>If the user agent has information on the likely encoding for this
      page, e.g. based on the encoding of the page when it was last visited,
@@ -38516,7 +38515,7 @@
      in predominantly Western demographics instead. Since these encodings can
      in many cases be distinguished by inspection, a user agent may
      heuristically decide which to use as a default.
-  </ul>
+  </ol>
 
   <h5 id=character0><span class=secno>8.2.2.2. </span>Character encoding
    requirements</h5>
@@ -40824,7 +40823,7 @@
     <p><a href="#create">Create an element for the token</a>.
 
    <li>
-    <p>Append the new element to the <a href="#current4">current node.</a>
+    <p>Append the new element to the <a href="#current4">current node</a>.
 
    <li>
     <p>If the algorithm that was invoked is the <a href="#generic">generic
@@ -40899,11 +40898,11 @@
 
    <li>If <var title="">node</var> is the first node in the stack of open
     elements, then set <var title="">last</var> to true; if, in addition, the
-    <var title="">context</var> element of the <span>HTML fragment parsing
-    algorithm is neither a <code><a href="#td">td</a></code> element nor a
-    <code><a href="#th">th</a></code> element, then set <var
-    title="">node</var> to the <var title="">context</var> element. (<a
-    href="#fragment">fragment case</a>)</span>
+    <var title="">context</var> element of the <a href="#html-fragment0">HTML
+    fragment parsing algorithm</a> is neither a <code><a
+    href="#td">td</a></code> element nor a <code><a href="#th">th</a></code>
+    element, then set <var title="">node</var> to the <var
+    title="">context</var> element. (<a href="#fragment">fragment case</a>)
 
    <li>If <var title="">node</var> is a <code>select</code> element, then
     switch the <a href="#insertion0">insertion mode</a> to "<a
@@ -42015,7 +42014,7 @@
      href="#tr">tr</a></code> element, the <code><a
      href="#body0">body</a></code> element, or the <code><a
      href="#html">html</a></code> element, then this is a <a
-     href="#parse0">parse error</a>.
+     href="#parse0">parse error</a>.</p>
 
     <p>Change the <a href="#insertion0">insertion mode</a> to "<a
      href="#after5" title="insertion mode: after body">after body</a>".</p>
@@ -42703,7 +42702,7 @@
 
     <p>Act as if a start tag token with the tag name "p" had been seen.</p>
 
-    <p>Act as if a start tag token with the tag name "label" had been seen.
+    <p>Act as if a start tag token with the tag name "label" had been seen.</p>
 
     <p>Act as if a stream of character tokens had been seen (see below for
      what they should say).</p>

Modified: source
===================================================================
--- source	2008-03-04 11:55:15 UTC (rev 1339)
+++ source	2008-03-04 20:42:19 UTC (rev 1340)
@@ -6371,7 +6371,7 @@
      LATIN SMALL LETTER U, a U+0052 LATIN CAPITAL LETTER R or a U+0072
      LATIN SMALL LETTER R, a U+004C LATIN CAPITAL LETTER L or a U+006C
      LATIN SMALL LETTER L, a U+003D EQUALS SIGN (<code
-     title="">=</code>), and then a valid URI (or IRI).</p>
+     title="">=</code>), and then a valid URI (or IRI).</li>
 
     </ul>
 
@@ -6519,7 +6519,7 @@
   <em>is</em> specified, then the <code>style</code> element must be
   the child of a <span>flow content</span> element, before any text
   nodes other than <span>inter-element whitespace</span>, and before
-  any elements other than other <code>style</code> elements.</dd>
+  any elements other than other <code>style</code> elements.</p>
 
   <p id="title-on-style">The <dfn
   title="attr-style-title"><code>title</code></dfn> attribute on
@@ -7237,13 +7237,13 @@
   <h5 id="outlines">Creating an outline</h5>
 
   <p>This section defines an algorithm for creating an
-  <dfn>outline</dfn> for a <span>sectioning content</code> element or
+  <dfn>outline</dfn> for a <span>sectioning content</span> element or
   a <span>sectioning root</span> element. It is defined in terms of a
   walk over the nodes of a DOM tree, in tree order, with each node
   being visited when it is <i>entered</i> and when it is <i>exited</i>
   during the walk.</p>
 
-  <p>The outline for a <span>sectioning content</code> element or a
+  <p>The outline for a <span>sectioning content</span> element or a
   <span>sectioning root</span> element consists of a list of one or
   more potentially nested sections. Each section can have one heading
   associated with it. The algorithm for the outline also associates
@@ -12894,7 +12894,7 @@
 
   <p>The <dfn><var>effective start</var></dfn> is the smaller of the
   <code title="dom-media-start">start</code> DOM attribute and the end
-  of the <span>media resource</span>.<p></li>
+  of the <span>media resource</span>.</p>
 
   <p>The <dfn
   title="attr-media-loopstart"><code>loopstart</code></dfn> content
@@ -13580,7 +13580,7 @@
    <dt>An "active" boolean</dt>
    <dd>A flag indicating whether the range is active or not.</dd>
 
-  </ul>
+  </dl>
 
   <p>The <dfn title="dom-media-addCueRange"><code>addCueRange(<var
   title="">className</var>, <var title="">start</var>, <var
@@ -15284,8 +15284,6 @@
    <li> <p>The shadow is in the bitmap <var title="">B</var>, and is
    rendered as part of the drawing model described below.</p> </li>
 
-  </li>
-
   </ol>
 
 
@@ -15750,9 +15748,9 @@
   title="">sw</var>, <var title="">sh</var>)</code></dfn> method must
   return an <code>ImageData</code> object representing a rectangle
   with a width in CSS pixels equal to the absolute magnitude of <var
-  title="">sw</var></span> and a height in CSS pixels equal to the
-  absolute magnitude of <var title="">sh</var></span>, filled with
-  transparent black.</p>
+  title="">sw</var> and a height in CSS pixels equal to the absolute
+  magnitude of <var title="">sh</var>, filled with transparent
+  black.</p>
 
   <p>The <dfn
   title="dom-context-2d-getImageData"><code>getImageData(<var
@@ -16142,7 +16140,7 @@
   returned. Where the output format allows it, the color of pixels in
   resources created by <code
   title="dom-canvas-toDataURL">toDataURL()</code> must match those
-  returned by the code
+  returned by the <code
   title="dom-context-2d-getImageData">getImageData()</code>
   method.</p>
 
@@ -19081,7 +19079,7 @@
   <code>meta</code> elements. If <span>scripting is enabled</span>,
   then the content model of a <code>noscript</code> element is text,
   except that invoking the <span>HTML fragment parsing
-  algorithm</code> with the <code>noscript</code> element as the <var
+  algorithm</span> with the <code>noscript</code> element as the <var
   title="">context</var> element and the text contents as the <var
   title="">input</var> must result in a list of nodes that consists
   only of <code>link</code>, <code>style</code>, and <code>meta</code>
@@ -25730,13 +25728,13 @@
 
    <li><p>If this is an <span title="concept-appcache-upgrade">upgrade
    attempt</span>, then add all the URIs of <span
-   title="concept-appcache-implicit">implicit entries</dfn> in <var
+   title="concept-appcache-implicit">implicit entries</span> in <var
    title="">cache</var> to <var title="">file list</var>, each flagged
    with "implicit entry".</p></li>
 
    <li><p>If this is an <span title="concept-appcache-upgrade">upgrade
    attempt</span>, then add all the URIs of <span
-   title="concept-appcache-dynamic">dynamic entries</dfn> in <var
+   title="concept-appcache-dynamic">dynamic entries</span> in <var
    title="">cache</var> to <var title="">file list</var>, each flagged
    with "dynamic entry".</p></li>
 
@@ -26624,7 +26622,7 @@
 
   <ol>
 
-   <li>If there is no longer a <code>Document</code> object for the
+   <li><p>If there is no longer a <code>Document</code> object for the
    entry in question, the user agent must <span>navigate</span> the
    browsing context to the location for that entry to preform an
    <span>entry update</span> of that entry, and abort these steps. The
@@ -26682,7 +26680,7 @@
      <span>active document</span> of the <span>browsing
      context</span>. (If it is a <span>top-level browsing
      context</span>, this might <a
-     href="#appcache-history-1">change</span> which <span>application
+     href="#appcache-history-1">change</a> which <span>application
      cache</span> it is associated with.)</li>
 
      <li>If the <span>specified entry</span> has a <span>browsing
@@ -27709,12 +27707,12 @@
 
    <li><p>If <var title="">official type</var> is "unknown/unknown" or
    "application/unknown", jump to the <em title="content-type
-   sniffing: unknown type">unknown type</em> step below.</p></p>
+   sniffing: unknown type">unknown type</em> step below.</p>
    <!-- In a study looking at many billions of pages whose first five
    characters were "<HTML", "unknown/unknown" was used to label
    documents about once for every 5000 pages labelled "text/html", and
    "application/unknown" was used about once for every 35000 pages
-   labelled "text/html". -->
+   labelled "text/html". --></li>
 
    <li><p>If <var title="">official type</var> ends in "+xml", or if
    it is either "text/xml" or "application/xml", then the the sniffed
@@ -27747,9 +27745,11 @@
    <li><p>Let <var title="">n</var> be the smaller of either 512 or
    the number of bytes already available.</p></li>
 
-   <li><p>If <var title="">n</var> is 4 or more, and the first bytes
-   of the file match one of the following byte sets:</p>
+   <li>
 
+    <p>If <var title="">n</var> is 4 or more, and the first bytes of
+    the file match one of the following byte sets:</p>
+
     <table>
      <thead>
       <tr>
@@ -27780,10 +27780,12 @@
 -->
     </table>
 
-   <p>...then the sniffed type of the resource is "text/plain".</p></li>
+    <p>...then the sniffed type of the resource is "text/plain".</p>
 
-   <p class="big-issue">Should we remove UTF-32 from the above?</p>
+    <p class="big-issue">Should we remove UTF-32 from the above?</p>
 
+   </li>
+
    <li><p>Otherwise, if any of the first <var title="">n</var> bytes
    of the resource are in one of the following byte ranges:</p>
 
@@ -29477,7 +29479,7 @@
 
      <li><p>Otherwise, the error callback did not return false, or
      there was no error callback. Jump to the last step in the overall
-     steps.</p></li
+     steps.</p></li>
 
     </ol>
 
@@ -29585,7 +29587,7 @@
   <p>The <dfn title="attr-hyperlink-target"><code>target</code></dfn>
   attribute, if present, must be a <span>valid browsing context
   name</span>. User agents use this name when <span>following
-  hyperlinks</span>.</p></p>
+  hyperlinks</span>.</p>
 
   <p>The <dfn id="ping"
   title="attr-hyperlink-ping"><code>ping</code></dfn> attribute, if
@@ -33475,7 +33477,7 @@
 
   <p>Once the end of the file is reached, the user agent must <a
   href="#dispatchMessage">dispatch the event</a> one final time, as
-  defined below.</p></dd>
+  defined below.</p>
 
 
   <p id="processField">The steps to <dfn title="">process the
@@ -33600,7 +33602,7 @@
    title="">Last-Event-ID</code> header with the value "1". The third
    block fires an event with data "second event", and also has an "id"
    field, this time with no value, which resets the last event ID to
-   the empty string (meaning no code title="">Last-Event-ID</code>
+   the empty string (meaning no <code title="">Last-Event-ID</code>
    header will now be sent in the event of a reconnection being
    attempted). Finally the last block just fires an event with the
    data "third event". Note that the last block doesn't have to end
@@ -35433,7 +35435,7 @@
   ampersand</dfn> is a U+0026 AMPERSAND (<code>&</code>) character
   that is followed by some <span title="syntax-text">text</span> other
   than a <span>space character</span>, a U+003C LESS-THAN SIGN
-  character ('&lt'), or another U+0026 AMPERSAND (<code>&</code>)
+  character ('<'), or another U+0026 AMPERSAND (<code>&</code>)
   character.</p>
 
 
@@ -35730,15 +35732,15 @@
          attribute's value as the string to parse. If an encoding is
          returned, let <var title="">charset</var> be that
          encoding. Otherwise, return to step 2 in these inner
-         steps.</li>
+         steps.</p></li>
 
-         <p>If <var title="">charset</var> is a UTF-16 encoding,
-         change it to UTF-8.</p>
+         <li><p>If <var title="">charset</var> is a UTF-16 encoding,
+         change it to UTF-8.</p></li>
 
-         <p>If <var title="">charset</var> is a supported character
-         encoding, then return the given encoding, with <span
-         title="concept-encoding-confidence">confidence</span>
-         <i>tentative</i>, and abort all these steps.</p>
+         <li><p>If <var title="">charset</var> is a supported
+         character encoding, then return the given encoding, with
+         <span title="concept-encoding-confidence">confidence</span>
+         <i>tentative</i>, and abort all these steps.</p></li>
 
          <li><p>Otherwise, return to step 2 in these inner
          steps.</p></li>
@@ -35923,7 +35925,7 @@
          title="">attribute value</var> whose codepoint is the same as
          the value of the byte at <var title="">position</var>.</li>
 
-         <li>Return to the second step in these substeps.</p>
+         <li>Return to the second step in these substeps.</li>
 
         </ol>
 
@@ -36155,7 +36157,7 @@
    <span>encoding sniffing algorithm</span> determined to be the
    encoding, and in the second pass through the parser if the first
    pass found that the encoding sniffing algorithm described in the
-   earlier section failed to find the right encoding.</p>
+   earlier section failed to find the right encoding.</li>
 
    <li>If all the bytes up to the last byte converted by the current
    decoder have the same Unicode interpretations in both the current
@@ -36244,7 +36246,7 @@
   <span>list of scripts that will execute asynchronously</span>, has
   <span>completed loading</span><!-- XXX xref -->. If one has, then it
   must be <span title="executing a script block">executed</span> and
-  removed from its list.</li>
+  removed from its list.</p>
 
   <p>The tokeniser state machine is as follows:</p>
 
@@ -38082,7 +38084,7 @@
    <li><p><span>Create an element for the token</span>.</p></li>
 
    <li><p>Append the new element to the <span>current
-   node</node>.</p></li>
+   node</span>.</p></li>
 
    <li><p>If the algorithm that was invoked is the <span>generic CDATA
    parsing algorithm</span>, switch the tokeniser's <span>content
@@ -38158,7 +38160,7 @@
    <li>If <var title="">node</var> is the first node in the stack of
    open elements, then set <var title="">last</var> to true; if, in
    addition, the <var title="">context</var> element of the <span>HTML
-   fragment parsing algorithm</var> is neither a <code>td</code>
+   fragment parsing algorithm</span> is neither a <code>td</code>
    element nor a <code>th</code> element, then set <var
    title="">node</var> to the <var title="">context</var>
    element. (<span>fragment case</span>)</li>
@@ -39145,7 +39147,7 @@
     <code>th</code> element, a <code>thead</code> element, a
     <code>tr</code> element, the <code>body</code> element, or the
     <code>html</code> element, then this is a <span>parse
-    error</span>.</li>
+    error</span>.</p>
 
     <p>Change the <span>insertion mode</span> to "<span
     title="insertion mode: after body">after body</span>".</p>
@@ -39881,18 +39883,21 @@
     resulting <code>form</code> element to the value of the
     "action" attribute of the token.</p>
 
-    <p>Act as if a start tag token with the tag name "hr" had been seen.</p>
+    <p>Act as if a start tag token with the tag name "hr" had been
+    seen.</p>
 
-    <p>Act as if a start tag token with the tag name "p" had been seen.</p>
+    <p>Act as if a start tag token with the tag name "p" had been
+    seen.</p>
 
-    <p>Act as if a start tag token with the tag name "label" had been seen.</p
+    <p>Act as if a start tag token with the tag name "label" had been
+    seen.</p>
 
-    <p>Act as if a stream of character tokens had been seen (see
-    below for what they should say).</p>
+    <p>Act as if a stream of character tokens had been seen (see below
+    for what they should say).</p>
 
-    <p>Act as if a start tag token with the tag name "input" had
-    been seen, with all the attributes from the "isindex" token
-    except "name", "action", and "prompt". Set the <code
+    <p>Act as if a start tag token with the tag name "input" had been
+    seen, with all the attributes from the "isindex" token except
+    "name", "action", and "prompt". Set the <code
     title="attr-input-name">name</code> attribute of the resulting
     <code>input</code> element to the value "<code
     title="">isindex</code>".</p>
@@ -39900,28 +39905,31 @@
     <p>Act as if a stream of character tokens had been seen (see
     below for what they should say).</p>
 
-    <p>Act as if an end tag token with the tag name "label" had been seen.</p>
+    <p>Act as if an end tag token with the tag name "label" had been
+    seen.</p>
 
-    <p>Act as if an end tag token with the tag name "p" had been seen.</p>
+    <p>Act as if an end tag token with the tag name "p" had been
+    seen.</p>
 
-    <p>Act as if a start tag token with the tag name "hr" had been seen.</p>
+    <p>Act as if a start tag token with the tag name "hr" had been
+    seen.</p>
 
-    <p>Act as if an end tag token with the tag name "form" had been seen.</p>
+    <p>Act as if an end tag token with the tag name "form" had been
+    seen.</p>
 
-    <p>If the token has an attribute with the name "prompt", then
-    the first stream of characters must be the same string as
-    given in that attribute, and the second stream of characters
-    must be empty. Otherwise, the two streams of character tokens
-    together should, together with the <code>input</code> element,
-    express the equivalent of "This is a searchable index. Insert
-    your search keywords here: (input field)" in the user's
-    preferred language.</p>
+    <p>If the token has an attribute with the name "prompt", then the
+    first stream of characters must be the same string as given in
+    that attribute, and the second stream of characters must be
+    empty. Otherwise, the two streams of character tokens together
+    should, together with the <code>input</code> element, express the
+    equivalent of "This is a searchable index. Insert your search
+    keywords here: (input field)" in the user's preferred
+    language.</p>
 
-    <p class="big-issue">
-    Then need to specify that if the form submission causes just a single
-    form control, whose name is "isindex", to be submitted, then we submit
-    just the value part, not the "isindex=" part.
-    </p>
+    <p class="big-issue"> Then need to specify that if the form
+    submission causes just a single form control, whose name is
+    "isindex", to be submitted, then we submit just the value part,
+    not the "isindex=" part.  </p>
 
    </dd>
 




More information about the Commit-Watchers mailing list