- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Sat, 06 Feb 2010 00:24:00 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv32636
Modified Files:
Overview.html
Log Message:
Make the note more pedantically correct, since there are parse error differences, it turns out. (whatwg r4673)
Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.3726
retrieving revision 1.3727
diff -u -d -r1.3726 -r1.3727
--- Overview.html 6 Feb 2010 00:14:56 -0000 1.3726
+++ Overview.html 6 Feb 2010 00:23:56 -0000 1.3727
@@ -57922,12 +57922,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>
Received on Saturday, 6 February 2010 00:24:01 UTC