[html5] r4486 - [e] (0) localName isn't affected by case conversions, so this note was previousl [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2010-01-05 03:32:23 -0800 (Tue, 05 Jan 2010)
New Revision: 4486

Modified:
   complete.html
   index
   source
Log:
[e] (0) localName isn't affected by case conversions, so this note was previously incorrect.
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=8376

Modified: complete.html
===================================================================
--- complete.html	2010-01-05 11:27:08 UTC (rev 4485)
+++ complete.html	2010-01-05 11:32:23 UTC (rev 4486)
@@ -9421,10 +9421,11 @@
 
     <p class=note>This doesn't apply to <code title="">Document.createElementNS()</code>. Thus, it is possible,
     by passing this last method a tag name in the wrong case, to
-    create an element that claims to have the tag name of an element
-    defined in this specification, but doesn't support its interfaces,
-    because it really has another tag name not accessible from the DOM
-    APIs.</p>
+    create an element that appears to have the same tag name as that
+    of an element defined in this specification when its <code title=dom-tagName>tagName</code> attribute is examined, but that
+    doesn't support the corresponding interfaces. The "real" element
+    name (unaffected by case conversions) can be obtained from the
+    <code title=dom-localName>localName</code> attribute.</p>
 
    </dd>
 

Modified: index
===================================================================
--- index	2010-01-05 11:27:08 UTC (rev 4485)
+++ index	2010-01-05 11:32:23 UTC (rev 4486)
@@ -9256,10 +9256,11 @@
 
     <p class=note>This doesn't apply to <code title="">Document.createElementNS()</code>. Thus, it is possible,
     by passing this last method a tag name in the wrong case, to
-    create an element that claims to have the tag name of an element
-    defined in this specification, but doesn't support its interfaces,
-    because it really has another tag name not accessible from the DOM
-    APIs.</p>
+    create an element that appears to have the same tag name as that
+    of an element defined in this specification when its <code title=dom-tagName>tagName</code> attribute is examined, but that
+    doesn't support the corresponding interfaces. The "real" element
+    name (unaffected by case conversions) can be obtained from the
+    <code title=dom-localName>localName</code> attribute.</p>
 
    </dd>
 

Modified: source
===================================================================
--- source	2010-01-05 11:27:08 UTC (rev 4485)
+++ source	2010-01-05 11:32:23 UTC (rev 4486)
@@ -9556,10 +9556,12 @@
     <p class="note">This doesn't apply to <code
     title="">Document.createElementNS()</code>. Thus, it is possible,
     by passing this last method a tag name in the wrong case, to
-    create an element that claims to have the tag name of an element
-    defined in this specification, but doesn't support its interfaces,
-    because it really has another tag name not accessible from the DOM
-    APIs.</p>
+    create an element that appears to have the same tag name as that
+    of an element defined in this specification when its <code
+    title="dom-tagName">tagName</code> attribute is examined, but that
+    doesn't support the corresponding interfaces. The "real" element
+    name (unaffected by case conversions) can be obtained from the
+    <code title="dom-localName">localName</code> attribute.</p>
 
    </dd>