[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 git-svn-id: http://svn.whatwg.org/webapps@8175 340c8d12-0b0e-0410-8428-c7bf67bfef74
whatwg · Sep 9, 2013 · d69e284 · d69e284
1 parent a9ad677
commit d69e284
Show file tree

Hide file tree

Showing 3 changed files with 15 additions and 12 deletions.
diff --git a/complete.html b/complete.html
@@ -86885,6 +86885,7 @@ <h5 id=other-parsing-state-flags><span class=secno>12.2.3.5 </span>Other parsing
   <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 @@ <h4 id=tokenization><span class=secno>12.2.4 </span><dfn>Tokenization</dfn></h4>
   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 @@ <h4 id=tokenization><span class=secno>12.2.4 </span><dfn>Tokenization</dfn></h4>
   <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>
 

diff --git a/index b/index
@@ -86885,6 +86885,7 @@ dictionary <dfn id=storageeventinit>StorageEventInit</dfn> : <a href=#eventinit>
   <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 @@ dictionary <dfn id=storageeventinit>StorageEventInit</dfn> : <a href=#eventinit>
   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 @@ dictionary <dfn id=storageeventinit>StorageEventInit</dfn> : <a href=#eventinit>
   <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>
 

diff --git a/source b/source
@@ -96977,6 +96977,7 @@ dictionary <dfn>StorageEventInit</dfn> : <span>EventInit</span> {
   <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 @@ dictionary <dfn>StorageEventInit</dfn> : <span>EventInit</span> {
   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 @@ dictionary <dfn>StorageEventInit</dfn> : <span>EventInit</span> {
   <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>