[html5] r7936 - [e] (0) Clarification. Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=219 [...]

whatwg at whatwg.org whatwg at whatwg.org
Fri Jun 7 14:44:51 PDT 2013


Author: ianh
Date: 2013-06-07 14:44:49 -0700 (Fri, 07 Jun 2013)
New Revision: 7936

Modified:
   complete.html
   index
   source
Log:
[e] (0) Clarification.
Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=21940
Affected topics: HTML Syntax and Parsing

Modified: complete.html
===================================================================
--- complete.html	2013-06-07 21:26:13 UTC (rev 7935)
+++ complete.html	2013-06-07 21:44:49 UTC (rev 7936)
@@ -86603,10 +86603,14 @@
   name must be compared to the other attributes on the same token;
   if there is already an attribute on the token with the exact same
   name, then this is a <a href=#parse-error>parse error</a> and the new
-  attribute must be dropped, along with the value that gets
-  associated with it (if any).</p>
+  attribute must be removed from the token.</p>
 
+  <p class=note>If an attribute is so removed from a token, it, along with the value that gets
+  associated with it, if any, are never subsequently used by the parser, and are therefore
+  effectively discarded. Removing the attribute in this way does not change its status as the
+  "current attribute" for the purposes of the tokenizer, however.</p>
 
+
   <h5 id=after-attribute-name-state><span class=secno>12.2.4.36 </span><dfn>After attribute name state</dfn></h5>
 
   <p>Consume the <a href=#next-input-character>next input character</a>:</p>

Modified: index
===================================================================
--- index	2013-06-07 21:26:13 UTC (rev 7935)
+++ index	2013-06-07 21:44:49 UTC (rev 7936)
@@ -86603,10 +86603,14 @@
   name must be compared to the other attributes on the same token;
   if there is already an attribute on the token with the exact same
   name, then this is a <a href=#parse-error>parse error</a> and the new
-  attribute must be dropped, along with the value that gets
-  associated with it (if any).</p>
+  attribute must be removed from the token.</p>
 
+  <p class=note>If an attribute is so removed from a token, it, along with the value that gets
+  associated with it, if any, are never subsequently used by the parser, and are therefore
+  effectively discarded. Removing the attribute in this way does not change its status as the
+  "current attribute" for the purposes of the tokenizer, however.</p>
 
+
   <h5 id=after-attribute-name-state><span class=secno>12.2.4.36 </span><dfn>After attribute name state</dfn></h5>
 
   <p>Consume the <a href=#next-input-character>next input character</a>:</p>

Modified: source
===================================================================
--- source	2013-06-07 21:26:13 UTC (rev 7935)
+++ source	2013-06-07 21:44:49 UTC (rev 7936)
@@ -96752,10 +96752,14 @@
   name must be compared to the other attributes on the same token;
   if there is already an attribute on the token with the exact same
   name, then this is a <span>parse error</span> and the new
-  attribute must be dropped, along with the value that gets
-  associated with it (if any).</p>
+  attribute must be removed from the token.</p>
 
+  <p class="note">If an attribute is so removed from a token, it, along with the value that gets
+  associated with it, if any, are never subsequently used by the parser, and are therefore
+  effectively discarded. Removing the attribute in this way does not change its status as the
+  "current attribute" for the purposes of the tokenizer, however.</p>
 
+
   <h5><dfn>After attribute name state</dfn></h5>
 
   <p>Consume the <span>next input character</span>:</p>




More information about the Commit-Watchers mailing list