[e] (0) Define 'insertion mode' earlier.

git-svn-id: http://svn.whatwg.org/webapps@1313 340c8d12-0b0e-0410-8428-c7bf67bfef74
whatwg · Mar 3, 2008 · 7f6b8c5 · 7f6b8c5
1 parent 6aeda20
commit 7f6b8c5
Show file tree

Hide file tree

Showing 2 changed files with 67 additions and 65 deletions.
diff --git a/index b/index
@@ -1617,8 +1617,8 @@
          <li><a href="#the-element"><span class=secno>8.2.4.5. </span>The
           element pointers</a>
 
-         <li><a href="#the-insertion"><span class=secno>8.2.4.6. </span>The
-          insertion mode</a>
+         <li><a href="#resetting"><span class=secno>8.2.4.6. </span>Resetting
+          the insertion mode</a>
 
          <li><a href="#the-initial"><span class=secno>8.2.4.7. </span>The
           initial insertion mode</a>
@@ -40469,16 +40469,39 @@ function receiver(e) {
    href="#hardwareLimitations">practical concerns</a> will likely force user
    agents to impose nesting depths.
 
-  <p>The tree construction stage has several pieces of state: a <a
-   href="#stack">stack of open elements</a>, a <a href="#list-of4">list of
-   active formatting elements</a>, a <a href="#head-element"><code
-   title="">head</code> element pointer</a>, a <a href="#form-element"><code
-   title="">form</code> element pointer</a>, and an <a
-   href="#insertion0">insertion mode</a>.
-
   <p>As each token is emitted from the tokeniser, the user agent must process
    the token according to the rules given in the section corresponding to the
-   current <a href="#insertion0">insertion mode</a>.
+   current <dfn id=insertion0>insertion mode</dfn>.
+
+  <p>Initially the <a href="#insertion0">insertion mode</a> is "<a
+   href="#initial" title="insertion mode: initial">initial</a>". It can
+   change to "<a href="#root-element0" title="insertion mode: root
+   element">root element</a>", "<a href="#in-head" title="insertion mode: in
+   head">in head</a>", "<a href="#in-head0" title="insertion mode: in head
+   noscript">in head noscript</a>", "<a href="#after4" title="insertion mode:
+   after head">after head</a>", "<a href="#in-body" title="insertion mode: in
+   body">in body</a>", "<a href="#in-table" title="insertion mode: in
+   table">in table</a>", "<a href="#in-caption" title="insertion mode: in
+   caption">in caption</a>", "<a href="#in-column" title="insertion mode: in
+   column group">in column group</a>", "<a href="#in-table0" title="insertion
+   mode: in table body">in table body</a>", "<a href="#in-row"
+   title="insertion mode: in row">in row</a>", "<a href="#in-cell"
+   title="insertion mode: in cell">in cell</a>", "<a href="#in-select"
+   title="insertion mode: in select">in select</a>", "<a href="#after5"
+   title="insertion mode: after body">after body</a>", "<a
+   href="#in-frameset" title="insertion mode: in frameset">in frameset</a>",
+   "<a href="#after6" title="insertion mode: after frameset">after
+   frameset</a>", "<a href="#after7" title="insertion mode: after after
+   body">after after body</a>", and "<a href="#after8" title="insertion mode:
+   after after frameset">after after frameset</a>" during the course of the
+   parsing, as described below. It affects how certain tokens are processed.
+
+  <p>In addition to the <a href="#insertion0">insertion mode</a>, the tree
+   construction stage has several pieces of state: a <a href="#stack">stack
+   of open elements</a>, a <a href="#list-of4">list of active formatting
+   elements</a>, a <a href="#head-element"><code title="">head</code> element
+   pointer</a>, and a <a href="#form-element"><code title="">form</code>
+   element pointer</a>.
 
   <h5 id=the-stack><span class=secno>8.2.4.1. </span>The stack of open
    elements</h5>
@@ -40848,30 +40871,8 @@ function receiver(e) {
    associate with forms in the face of dramatically bad markup, for
    historical reasons.
 
-  <h5 id=the-insertion><span class=secno>8.2.4.6. </span>The insertion mode</h5>
-
-  <p>Initially the <dfn id=insertion0>insertion mode</dfn> is "<a
-   href="#initial" title="insertion mode: initial">initial</a>". It can
-   change to "<a href="#root-element0" title="insertion mode: root
-   element">root element</a>", "<a href="#in-head" title="insertion mode: in
-   head">in head</a>", "<a href="#in-head0" title="insertion mode: in head
-   noscript">in head noscript</a>", "<a href="#after4" title="insertion mode:
-   after head">after head</a>", "<a href="#in-body" title="insertion mode: in
-   body">in body</a>", "<a href="#in-table" title="insertion mode: in
-   table">in table</a>", "<a href="#in-caption" title="insertion mode: in
-   caption">in caption</a>", "<a href="#in-column" title="insertion mode: in
-   column group">in column group</a>", "<a href="#in-table0" title="insertion
-   mode: in table body">in table body</a>", "<a href="#in-row"
-   title="insertion mode: in row">in row</a>", "<a href="#in-cell"
-   title="insertion mode: in cell">in cell</a>", "<a href="#in-select"
-   title="insertion mode: in select">in select</a>", "<a href="#after5"
-   title="insertion mode: after body">after body</a>", "<a
-   href="#in-frameset" title="insertion mode: in frameset">in frameset</a>",
-   "<a href="#after6" title="insertion mode: after frameset">after
-   frameset</a>", "<a href="#after7" title="insertion mode: after after
-   body">after after body</a>", and "<a href="#after8" title="insertion mode:
-   after after frameset">after after frameset</a>" during the course of the
-   parsing, as described below. It affects how certain tokens are processed.
+  <h5 id=resetting><span class=secno>8.2.4.6. </span>Resetting the insertion
+   mode</h5>
 
   <p>When the steps below require the UA to <dfn id=reset>reset the insertion
    mode appropriately</dfn>, it means the UA must follow these steps:

diff --git a/source b/source
@@ -37754,15 +37754,39 @@ function receiver(e) {
   concerns</a> will likely force user agents to impose nesting
   depths.</p>
 
-  <p>The tree construction stage has several pieces of state: a
-  <span>stack of open elements</span>, a <span>list of active
-  formatting elements</span>, a <span><code title="">head</code>
-  element pointer</span>, a <span><code title="">form</code> element
-  pointer</span>, and an <span>insertion mode</span>.</p>
-
   <p>As each token is emitted from the tokeniser, the user agent must
   process the token according to the rules given in the section
-  corresponding to the current <span>insertion mode</span>.</p>
+  corresponding to the current <dfn>insertion mode</dfn>.</p>
+
+  <p>Initially the <span>insertion mode</span> is "<span
+  title="insertion mode: initial">initial</span>". It can change to
+  "<span title="insertion mode: root element">root element</span>",
+  "<span title="insertion mode: in head">in head</span>", "<span
+  title="insertion mode: in head noscript">in head noscript</span>",
+  "<span title="insertion mode: after head">after head</span>", "<span
+  title="insertion mode: in body">in body</span>", "<span
+  title="insertion mode: in table">in table</span>", "<span
+  title="insertion mode: in caption">in caption</span>", "<span
+  title="insertion mode: in column group">in column group</span>",
+  "<span title="insertion mode: in table body">in table body</span>",
+  "<span title="insertion mode: in row">in row</span>", "<span
+  title="insertion mode: in cell">in cell</span>", "<span
+  title="insertion mode: in select">in select</span>", "<span
+  title="insertion mode: after body">after body</span>", "<span
+  title="insertion mode: in frameset">in frameset</span>", "<span
+  title="insertion mode: after frameset">after frameset</span>",
+  "<span title="insertion mode: after after body">after after
+  body</span>", and "<span title="insertion mode: after after
+  frameset">after after frameset</span>" during the course of the
+  parsing, as described below. It affects how certain tokens are
+  processed.</p>
+
+  <p>In addition to the <span>insertion mode</span>, the tree
+  construction stage has several pieces of state: a <span>stack of
+  open elements</span>, a <span>list of active formatting
+  elements</span>, a <span><code title="">head</code> element
+  pointer</span>, and a <span><code title="">form</code> element
+  pointer</span>.</p>
 
 
   <h5>The stack of open elements</h5>
@@ -38101,30 +38125,7 @@ function receiver(e) {
   markup, for historical reasons.</p>
 
 
-  <h5>The insertion mode</h5>
-
-  <p>Initially the <dfn>insertion mode</dfn> is "<span
-  title="insertion mode: initial">initial</span>". It can change to
-  "<span title="insertion mode: root element">root element</span>",
-  "<span title="insertion mode: in head">in head</span>", "<span
-  title="insertion mode: in head noscript">in head noscript</span>",
-  "<span title="insertion mode: after head">after head</span>", "<span
-  title="insertion mode: in body">in body</span>", "<span
-  title="insertion mode: in table">in table</span>", "<span
-  title="insertion mode: in caption">in caption</span>", "<span
-  title="insertion mode: in column group">in column group</span>",
-  "<span title="insertion mode: in table body">in table body</span>",
-  "<span title="insertion mode: in row">in row</span>", "<span
-  title="insertion mode: in cell">in cell</span>", "<span
-  title="insertion mode: in select">in select</span>", "<span
-  title="insertion mode: after body">after body</span>", "<span
-  title="insertion mode: in frameset">in frameset</span>", "<span
-  title="insertion mode: after frameset">after frameset</span>",
-  "<span title="insertion mode: after after body">after after
-  body</span>", and "<span title="insertion mode: after after
-  frameset">after after frameset</span>" during the course of the
-  parsing, as described below. It affects how certain tokens are
-  processed.</p>
+  <h5>Resetting the insertion mode</h5>
 
   <p>When the steps below require the UA to <dfn>reset the insertion
   mode appropriately</dfn>, it means the UA must follow these