[html5] r4673 - [e] (0) Make the note more pedantically correct, since there are parse error dif [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2010-02-05 16:23:51 -0800 (Fri, 05 Feb 2010)
New Revision: 4673

Modified:
   complete.html
   index
   source
Log:
[e] (0) Make the note more pedantically correct, since there are parse error differences, it turns out.
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=8699

Modified: complete.html
===================================================================
--- complete.html	2010-02-06 00:14:51 UTC (rev 4672)
+++ complete.html	2010-02-06 00:23:51 UTC (rev 4673)
@@ -78052,12 +78052,13 @@
        <dd>Leave the tokenizer in the <a href=#data-state>data state</a>.</dd>
 
       </dl><p class=note>For performance reasons, an implementation that
-      uses the actual state machine described in this specification
-      directly could use the PLAINTEXT state instead of the RAWTEXT
-      and script data states where those are mentioned in the list
-      above. They are equivalent, since there is no <a href=#appropriate-end-tag-token>appropriate
-      end tag token</a> in the fragment case, but involve far fewer
-      state transitions.</p>
+      does not report errors and that uses the actual state machine
+      described in this specification directly could use the PLAINTEXT
+      state instead of the RAWTEXT and script data states where those
+      are mentioned in the list above. Except for rules regarding
+      parse errors, they are equivalent, since there is no
+      <a href=#appropriate-end-tag-token>appropriate end tag token</a> in the fragment case, yet
+      they involve far fewer state transitions.</p>
 
      </li>
 

Modified: index
===================================================================
--- index	2010-02-06 00:14:51 UTC (rev 4672)
+++ index	2010-02-06 00:23:51 UTC (rev 4673)
@@ -72347,12 +72347,13 @@
        <dd>Leave the tokenizer in the <a href=#data-state>data state</a>.</dd>
 
       </dl><p class=note>For performance reasons, an implementation that
-      uses the actual state machine described in this specification
-      directly could use the PLAINTEXT state instead of the RAWTEXT
-      and script data states where those are mentioned in the list
-      above. They are equivalent, since there is no <a href=#appropriate-end-tag-token>appropriate
-      end tag token</a> in the fragment case, but involve far fewer
-      state transitions.</p>
+      does not report errors and that uses the actual state machine
+      described in this specification directly could use the PLAINTEXT
+      state instead of the RAWTEXT and script data states where those
+      are mentioned in the list above. Except for rules regarding
+      parse errors, they are equivalent, since there is no
+      <a href=#appropriate-end-tag-token>appropriate end tag token</a> in the fragment case, yet
+      they involve far fewer state transitions.</p>
 
      </li>
 

Modified: source
===================================================================
--- source	2010-02-06 00:14:51 UTC (rev 4672)
+++ source	2010-02-06 00:23:51 UTC (rev 4673)
@@ -89074,12 +89074,13 @@
       </dl>
 
       <p class="note">For performance reasons, an implementation that
-      uses the actual state machine described in this specification
-      directly could use the PLAINTEXT state instead of the RAWTEXT
-      and script data states where those are mentioned in the list
-      above. They are equivalent, since there is no <span>appropriate
-      end tag token</span> in the fragment case, but involve far fewer
-      state transitions.</p>
+      does not report errors and that uses the actual state machine
+      described in this specification directly could use the PLAINTEXT
+      state instead of the RAWTEXT and script data states where those
+      are mentioned in the list above. Except for rules regarding
+      parse errors, they are equivalent, since there is no
+      <span>appropriate end tag token</span> in the fragment case, yet
+      they involve far fewer state transitions.</p>
 
      </li>