[html5] r8175 - [e] (0) Rejigger the create vs emit token note Fixing https://www.w3.org/Bugs/Pu [...]

whatwg at whatwg.org whatwg at whatwg.org
Mon Sep 9 15:41:38 PDT 2013


Author: ianh
Date: 2013-09-09 15:41:37 -0700 (Mon, 09 Sep 2013)
New Revision: 8175

Modified:
   complete.html
   index
   source
Log:
[e] (0) Rejigger the create vs emit token note
Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=23088
Affected topics: HTML Syntax and Parsing

Modified: complete.html
===================================================================
--- complete.html	2013-09-09 22:20:50 UTC (rev 8174)
+++ complete.html	2013-09-09 22:41:37 UTC (rev 8175)
@@ -86885,6 +86885,7 @@
   <div class=impl>
 
   <h4 id=tokenization><span class=secno>12.2.4 </span><dfn>Tokenization</dfn></h4>
+<!--CLEANUP-->
 
   <p>Implementations must act as if they used the following state
   machine to tokenize HTML. The state machine must start in the
@@ -86925,6 +86926,10 @@
   using the <a href=#dynamic-markup-insertion>dynamic markup insertion</a> APIs to insert
   characters into the stream being tokenized.)</p>
 
+  <p class=note>Creating a token and emitting it are distinct actions. It is possible for a token
+  to be created but implicitly abandoned (never emitted), e.g. if the file ends unexpectedly while
+  processing the characters that are being parsed into a start tag token.</p>
+
   <p>When a start tag token is emitted with its <i>self-closing
   flag</i> set, if the flag is not <dfn id=acknowledge-self-closing-flag title="acknowledge
   self-closing flag">acknowledged</dfn> when it is processed by the
@@ -86933,10 +86938,6 @@
   <p>When an end tag token is emitted with attributes, that is a
   <a href=#parse-error>parse error</a>.</p>
 
-  <p class=note>Creating a token and emitting it are distinct actions. It is possible for a token
-  to be implicitly abandoned, e.g. if the file ends unexpectedly while parsing the characters that
-  are being parsed into a start tag token.</p>
-
   <p>When an end tag token is emitted with its <i>self-closing
   flag</i> set, that is a <a href=#parse-error>parse error</a>.</p>
 

Modified: index
===================================================================
--- index	2013-09-09 22:20:50 UTC (rev 8174)
+++ index	2013-09-09 22:41:37 UTC (rev 8175)
@@ -86885,6 +86885,7 @@
   <div class=impl>
 
   <h4 id=tokenization><span class=secno>12.2.4 </span><dfn>Tokenization</dfn></h4>
+<!--CLEANUP-->
 
   <p>Implementations must act as if they used the following state
   machine to tokenize HTML. The state machine must start in the
@@ -86925,6 +86926,10 @@
   using the <a href=#dynamic-markup-insertion>dynamic markup insertion</a> APIs to insert
   characters into the stream being tokenized.)</p>
 
+  <p class=note>Creating a token and emitting it are distinct actions. It is possible for a token
+  to be created but implicitly abandoned (never emitted), e.g. if the file ends unexpectedly while
+  processing the characters that are being parsed into a start tag token.</p>
+
   <p>When a start tag token is emitted with its <i>self-closing
   flag</i> set, if the flag is not <dfn id=acknowledge-self-closing-flag title="acknowledge
   self-closing flag">acknowledged</dfn> when it is processed by the
@@ -86933,10 +86938,6 @@
   <p>When an end tag token is emitted with attributes, that is a
   <a href=#parse-error>parse error</a>.</p>
 
-  <p class=note>Creating a token and emitting it are distinct actions. It is possible for a token
-  to be implicitly abandoned, e.g. if the file ends unexpectedly while parsing the characters that
-  are being parsed into a start tag token.</p>
-
   <p>When an end tag token is emitted with its <i>self-closing
   flag</i> set, that is a <a href=#parse-error>parse error</a>.</p>
 

Modified: source
===================================================================
--- source	2013-09-09 22:20:50 UTC (rev 8174)
+++ source	2013-09-09 22:41:37 UTC (rev 8175)
@@ -96977,6 +96977,7 @@
   <div class="impl">
 
   <h4><dfn>Tokenization</dfn></h4>
+<!--CLEANUP-->
 
   <p>Implementations must act as if they used the following state
   machine to tokenize HTML. The state machine must start in the
@@ -97017,6 +97018,10 @@
   using the <span>dynamic markup insertion</span> APIs to insert
   characters into the stream being tokenized.)</p>
 
+  <p class="note">Creating a token and emitting it are distinct actions. It is possible for a token
+  to be created but implicitly abandoned (never emitted), e.g. if the file ends unexpectedly while
+  processing the characters that are being parsed into a start tag token.</p>
+
   <p>When a start tag token is emitted with its <i>self-closing
   flag</i> set, if the flag is not <dfn title="acknowledge
   self-closing flag">acknowledged</dfn> when it is processed by the
@@ -97025,10 +97030,6 @@
   <p>When an end tag token is emitted with attributes, that is a
   <span>parse error</span>.</p>
 
-  <p class="note">Creating a token and emitting it are distinct actions. It is possible for a token
-  to be implicitly abandoned, e.g. if the file ends unexpectedly while parsing the characters that
-  are being parsed into a start tag token.</p>
-
   <p>When an end tag token is emitted with its <i>self-closing
   flag</i> set, that is a <span>parse error</span>.</p>
 




More information about the Commit-Watchers mailing list