[e] (0) more markup fixes

git-svn-id: http://svn.whatwg.org/webapps@552 340c8d12-0b0e-0410-8428-c7bf67bfef74

index

@@ -22,7 +22,7 @@
 
    <h1 id=web-applications>Web Applications 1.0</h1>
 
-   <h2 class="no-num no-toc" id=working>Working Draft &mdash; 2 February 2007</h2>
+   <h2 class="no-num no-toc" id=working>Working Draft &mdash; 3 February 2007</h2>
 
    <p>You can take part in this work. <a
     href="http://www.whatwg.org/mailing-list">Join the working group's
@@ -736,7 +736,7 @@
         </ul>
       </ul>
 
-     <li><a href="#scripting"><span class=secno>3.17. </span>Scripting</a>
+     <li><a href="#scripting0"><span class=secno>3.17. </span>Scripting</a>
       <ul class=toc>
        <li><a href="#script"><span class=secno>3.17.1. </span>The <dfn
         id=script1><code>script</code></dfn> element</a>
@@ -877,7 +877,7 @@
        <li><a href="#running"><span class=secno>4.2.1. </span>Running
         executable code</a>
 
-       <li><a href="#scripting0"><span class=secno>4.2.2. </span>Scripting
+       <li><a href="#scripting1"><span class=secno>4.2.2. </span>Scripting
         contexts</a>
 
        <li><a href="#threads"><span class=secno>4.2.3. </span>Threads</a>
@@ -1679,7 +1679,7 @@
 
    <dd>
     <p>Implementations that do not support scripting (or which have their
-     scripting features <a href="#scripting1" title="scripting is
+     scripting features <a href="#scripting2" title="scripting is
      disabled">disabled</a>) are exempt from supporting the events and DOM
      interfaces mentioned in this specification. For the parts of this
      specification that are defined in terms of an events model or in terms
@@ -1704,8 +1704,8 @@
      material).</p>
 
     <p>Conformance checkers must check that the input document conforms when
-     <a href="#scripting1">scripting is disabled</a>, and should also check
-     that the input document conforms when <a href="#scripting2">scripting is
+     <a href="#scripting2">scripting is disabled</a>, and should also check
+     that the input document conforms when <a href="#scripting3">scripting is
      enabled</a>. (This is only a "SHOULD" and not a "MUST" requirement
      because it has been proven to be impossible. <a
      href="#refsHALTINGPROBLEM">[HALTINGPROBLEM]</a>)</p>
@@ -5766,8 +5766,9 @@ http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C%21DOCTYPE%20HTML%3E%0
   <p>The <code title=attr-dir><a href="#dir0">dir</a></code> attribute
    specifies the element's text directionality. The attribute is an <a
    href="#enumerated">enumerated attribute</a> with the keyword <code
-   title="">ltr</code> mapping to the state <em>ltr</em>, and the keyword rtl
-   mapping to the state <em>rtl</em>. The attribute has no defaults.
+   title="">ltr</code> mapping to the state <em>ltr</em>, and the keyword
+   <code title="">rtl</code> mapping to the state <em>rtl</em>. The attribute
+   has no defaults.
 
   <p>If the attribute has the state <em>ltr</em>, the element's
    directionality is left-to-right. If the attribute has the state
@@ -10864,13 +10865,11 @@ her&mdash;&lt;/i>&lt;/p>
     href="#b0">b</a></code> element to highlight key words without marking
     them up as important:</p>
 
-   <pre>&lt;p>The &lt;b>frobonitor&lt;/b> and &lt;b>barbinator&lt;/b> components are fried.&lt;/p>
-   </pre>
+   <pre>&lt;p>The &lt;b>frobonitor&lt;/b> and &lt;b>barbinator&lt;/b> components are fried.&lt;/p></pre>
 
    <p>The following would be <em>incorrect</em> usage:</p>
 
-   <pre>&lt;p>&lt;b>WARNING!&lt;/b> Do not frob the barbinator!&lt;/p>
-   </pre>
+   <pre>&lt;p>&lt;b>WARNING!&lt;/b> Do not frob the barbinator!&lt;/p></pre>
 
    <p>In the previous example, the correct element to use would have been
     <code><a href="#strong0">strong</a></code>, not <code><a
@@ -11853,9 +11852,8 @@ brighter. A &lt;b>rat&lt;/b> scurries past the corner wall.&lt;/p></pre>
          href="#refsNPAPI">[NPAPI]</a></p>
 
         <p class=big-issue>this doesn't completely duplicate the navigation
-         section, since it handles <object>
-         <param>
-         , etc, but surely some work should be done to work with it</object></p>
+         section, since it handles &lt;param>, etc, but surely some work
+         should be done to work with it</p>
 
        <dt>If the type of the resource is an <span>XML MIME
         type</span><!-- XXX xref -->
@@ -15228,7 +15226,7 @@ interface <dfn id=imagedata>ImageData</dfn> {
    href="http://whatwg.org/specs/web-forms/current-work/#form-submission">WF2</a>
    for now
 
-  <h3 id=scripting><span class=secno>3.17. </span>Scripting</h3>
+  <h3 id=scripting0><span class=secno>3.17. </span>Scripting</h3>
 
   <h4 id=script><span class=secno>3.17.1. </span>The <dfn
    id=script2><code>script</code></dfn> element</h4>
@@ -15304,9 +15302,9 @@ interface <dfn id=imagedata>ImageData</dfn> {
    href="#refsRFC2046">[RFC2046]</a>
 
   <p>The <dfn id=defer title=attr-script-defer><code>defer</code></dfn> and
-   <dfn id=async title=attr-script-async>async</dfn> attributes are <a
-   href="#boolean0" title="boolean attribute">boolean attributes</a> that
-   indicate how the script should be executed.
+   <dfn id=async title=attr-script-async><code>async</code></dfn> attributes
+   are <a href="#boolean0" title="boolean attribute">boolean attributes</a>
+   that indicate how the script should be executed.
 
   <p>There are three possible modes that can be selected using these
    attributes. If the <code title=attr-script-defer><a
@@ -15598,13 +15596,13 @@ interface <dfn id=imagedata>ImageData</dfn> {
   <h4 id=the-noscript><span class=secno>3.17.2. </span>The <dfn
    id=noscript0><code>noscript</code></dfn> element</h4>
 
-  <p>When <a href="#scripting1">scripting is disabled</a>: <a
+  <p>When <a href="#scripting2">scripting is disabled</a>: <a
    href="#transparent0">transparent</a> <a href="#block-level1"
    title="block-level elements">block-level element</a>, and <a
    href="#transparent0">transparent</a> <a href="#strictly">strictly
    inline-level content</a>.
 
-  <p>When <a href="#scripting2">scripting is enabled</a>: <a
+  <p>When <a href="#scripting3">scripting is enabled</a>: <a
    href="#block-level1" title="block-level elements">block-level element</a>,
    and <a href="#strictly">strictly inline-level content</a>.
 
@@ -15625,11 +15623,11 @@ interface <dfn id=imagedata>ImageData</dfn> {
 
    <dt>Content model:
 
-   <dd>When <a href="#scripting1">scripting is disabled</a>: <a
+   <dd>When <a href="#scripting2">scripting is disabled</a>: <a
     href="#transparent0">transparent</a>, but there must be no <code><a
     href="#noscript0">noscript</a></code> element descendants.
 
-   <dd>When <a href="#scripting2">scripting is enabled</a>: Text that
+   <dd>When <a href="#scripting3">scripting is enabled</a>: Text that
     conforms to the requirements given in the prose.
 
    <dt>Element-specific attributes:
@@ -15657,14 +15655,14 @@ interface <dfn id=imagedata>ImageData</dfn> {
   <p>When used in <a href="#html-">HTML documents</a>, the allowed content
    model depends on whether scripting is enabled or not.
 
-  <p>If <a href="#scripting1">scripting is disabled</a>, then the content
+  <p>If <a href="#scripting2">scripting is disabled</a>, then the content
    model of a <code><a href="#noscript0">noscript</a></code> element is <a
    href="#transparent0">transparent</a>, with the additional restriction that
    a <code><a href="#noscript0">noscript</a></code> element must not have a
    <code><a href="#noscript0">noscript</a></code> element as an ancestor
    (that is, <code><a href="#noscript0">noscript</a></code> can't be nested).
 
-  <p>If <a href="#scripting2">scripting is enabled</a>, then the content
+  <p>If <a href="#scripting3">scripting is enabled</a>, then the content
    model of a <code><a href="#noscript0">noscript</a></code> element is text,
    except that the text must be such that running the following algorithm
    results in a conforming document with no <code><a
@@ -18569,7 +18567,7 @@ XXX selection ranges -->
     <p>Start fetching the specified resource, as appropriate (e.g. performing
      an HTTP GET or POST operation, or reading the file from disk, or
      executing script in the case of a <a href="#the-javascript0"
-     title="javascript protocol"><code javascript: title=""></code> URI</a>).
+     title="javascript protocol"><code title="">javascript:</code> URI</a>).
      If this results in a redirect, return to step 2 with the new resource.
 
    <li>
@@ -18748,11 +18746,11 @@ XXX selection ranges -->
 
    <li>
     <p>Let <var title="">official type</var> be the type given by the
-     <span>Content-Type metadata for the resource (in
+     <span>Content-Type metadata</span> for the resource (in
      lowercase<!-- XXX ASCII case folding -->, ignoring any parameters). If
      there is no such type, jump to the <em title="content-type sniffing:
      unknown type"><a href="#content-type10">unknown type</a></em> step
-     below.</span>
+     below.
 
    <li>
     <p>If the <var title="">official type</var> ends in "+xml", or if it is
@@ -19106,8 +19104,9 @@ XXX selection ranges -->
 
      <dd>Increase <var title="">pos</var> by 1 and go to the next step.
 
-     <dt>If it is anything else, the sniffed type of the resource is
-      "text/html". Abort these steps.
+     <dt>If it is anything else
+
+     <dd>The sniffed type of the resource is "text/html". Abort these steps.
     </dl>
 
    <li>
@@ -19388,51 +19387,51 @@ XXX selection ranges -->
    of author-provided code. When the user agent is configured such that
    author-provided code does not execute, or if the user agent is implemented
    so as to never execute author-provided code, it is said that <dfn
-   id=scripting1>scripting is disabled</dfn>. When author-provided code
-   <em>does</em> execute, <dfn id=scripting2>scripting is enabled</dfn>. A
+   id=scripting2>scripting is disabled</dfn>. When author-provided code
+   <em>does</em> execute, <dfn id=scripting3>scripting is enabled</dfn>. A
    user agent with scripting disabled is a <a href="#non-scripted"
    title="User agents with no scripting support">user agent with no scripting
    support</a> for the purposes of conformance.
 
-  <h4 id=scripting0><span class=secno>4.2.2. </span>Scripting contexts</h4>
+  <h4 id=scripting1><span class=secno>4.2.2. </span>Scripting contexts</h4>
 
   <p>Each <code>Document</code> in a <a href="#browsing">browsing context</a>
-   has an associated <dfn id=scripting3>scripting context</dfn>.
+   has an associated <dfn id=scripting4>scripting context</dfn>.
 
   <h4 id=threads><span class=secno>4.2.3. </span>Threads</h4>
 
-  <p>Each <a href="#scripting3">scripting context</a> is defined as having a
+  <p>Each <a href="#scripting4">scripting context</a> is defined as having a
    list of zero or more <dfn id=reachable>reachable scripting contexts</dfn>.
    These are:
 
   <ul>
-   <li>All the <a href="#scripting3" title="scripting context">scripting
+   <li>All the <a href="#scripting4" title="scripting context">scripting
     contexts</a> of all the <code>Document</code>s in each nested <a
     href="#browsing">browsing context</a> inside the scripting context's
     <code>Document</code>.
 
-   <li>The <a href="#scripting3">scripting context</a> of the
+   <li>The <a href="#scripting4">scripting context</a> of the
     <code>Document</code> that contains the <code>Document</code>'s <a
     href="#browsing">browsing context</a>.
 
-   <li>All the <a href="#scripting3" title="scripting context">scripting
+   <li>All the <a href="#scripting4" title="scripting context">scripting
     contexts</a> of all the <code>Document</code>s associated with any <a
     href="#top-level" title="top-level browsing context">top-level browsing
     contexts</a> that were opened from a <code>Document</code> associated
-    with the <a href="#scripting3">scripting context</a>'s
+    with the <a href="#scripting4">scripting context</a>'s
     <code>Document</code>'s <a href="#browsing">browsing context</a>.
 
-   <li>All the <a href="#scripting3" title="scripting context">scripting
+   <li>All the <a href="#scripting4" title="scripting context">scripting
     contexts</a> of all the <code>Document</code>s associated with the <a
     href="#top-level" title="top-level browsing context">top-level browsing
     contexts</a> of the <a href="#browsing">browsing context</a> of the
     <code><a href="#windowhtml">WindowHTML</a></code> object returned by the
-    <a href="#scripting3">scripting context</a>'s <code>Document</code>'s
+    <a href="#scripting4">scripting context</a>'s <code>Document</code>'s
     <code><a href="#windowhtml">WindowHTML</a></code>'s <code
     title=dom-opener>opener</code> attribute.
   </ul>
 
-  <p>The transitive closure of all the <a href="#scripting3" title="scripting
+  <p>The transitive closure of all the <a href="#scripting4" title="scripting
    context">scripting contexts</a> that are <a href="#reachable">reachable
    scripting contexts</a> consists of a <dfn id=unit-of>unit of related
    scripting contexts</dfn>.
@@ -19696,6 +19695,8 @@ XXX selection ranges -->
     is targetted at or bubbles through the element.
 
    <dt>...more events...
+
+   <dd>
   </dl>
 
   <p>All event handler attributes on an element, whether set to null or to a
@@ -25581,7 +25582,7 @@ http://developer.apple.com/documentation/AppleApplications/Conceptual/SafariJSPr
    <p>In the following document fragment, the emphasised parts indicate the
     selection.</p>
 
-   <pre>&lt;p>The cute girl likes <em>the </em>&lt;cite><em>Oxford English</em> Dictionary&lt;/cite>.&lt/p></pre>
+   <pre>&lt;p>The cute girl likes <em>the </em>&lt;cite><em>Oxford English</em> Dictionary&lt;/cite>.&lt;/p></pre>
 
    <p>If a script invoked <code
     title="">window.getSelection().toString()</code>, the return value would
@@ -26178,7 +26179,7 @@ document.getElementById('stock').addEventListener('stock change',
     var data = event.data.split('\n');
     updateStocks(data[0], data[1], data[2]);
   }, false);
-&lt;/script&gt</pre>
+&lt;/script&gt;</pre>
 
    <p>...where updateStocks is a function defined as:
 
@@ -27804,7 +27805,8 @@ function receiver(e) {
   <p>The rules for parsing <a href="#xml-documents">XML documents</a> (and
    thus <a href="#xhtml5">XHTML</a> documents) into DOM trees are covered by
    the XML and Namespaces in XML specifications, and are out of scope of this
-   specification. <a href="#refs"></a> <!-- XXX refs -->
+   specification. <a href="#refsXML">[XML]</a> <a
+   href="#refsXMLNS">[XMLNS]</a> <!-- XXX refs -->
 
   <p>For <a href="#html-">HTML documents</a>, user agents must use the
    parsing rules described in this section to generate the DOM trees.
@@ -31016,7 +31018,7 @@ simplified explanation instead:
         "noframes"
 
        <dt>A start tag whose tag name is "noscript", if <a
-        href="#scripting2">scripting is enabled</a>:
+        href="#scripting3">scripting is enabled</a>:
 
        <dd>
         <p><a href="#create">Create an element for the token</a>.</p>
@@ -31078,7 +31080,7 @@ simplified explanation instead:
        <!-- add keygen if we add the start tag -->
 
        <dt>An end tag whose tag name is "noscript", if <a
-        href="#scripting2">scripting is enabled</a>:
+        href="#scripting3">scripting is enabled</a>:
 
        <dd>
         <p><a href="#parse">Parse error</a>. Ignore the token.</p>