html5/spec-author-view Overview.html,1.578,1.579 apis-in-html-documents.html,1.9,1.10 spec.html,1.583,1.584

Update of /sources/public/html5/spec-author-view
In directory hutz:/tmp/cvs-serv23945

Modified Files:
	Overview.html apis-in-html-documents.html spec.html 
Log Message:
copypasta (whatwg r4487)

[updated by splitter]


Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec-author-view/Overview.html,v
retrieving revision 1.578
retrieving revision 1.579
diff -u -d -r1.578 -r1.579
--- Overview.html	5 Jan 2010 11:27:21 -0000	1.578
+++ Overview.html	5 Jan 2010 11:37:20 -0000	1.579
@@ -281,7 +281,7 @@
    </dl><p>This specification is available in the following formats: 
     <a href="spec.html">single page HTML</a>,
     <a href="Overview.html">multipage HTML</a>.
-This is revision 1.3584.
+This is revision 1.3587.
    </p>
    <p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>
    &#169; 2009 <a href="http://www.w3.org/"><abbr title="World Wide

Index: apis-in-html-documents.html
===================================================================
RCS file: /sources/public/html5/spec-author-view/apis-in-html-documents.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -d -r1.9 -r1.10
--- apis-in-html-documents.html	3 Jan 2010 15:15:05 -0000	1.9
+++ apis-in-html-documents.html	5 Jan 2010 11:37:20 -0000	1.10
@@ -295,10 +295,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>
 

Index: spec.html
===================================================================
RCS file: /sources/public/html5/spec-author-view/spec.html,v
retrieving revision 1.583
retrieving revision 1.584
diff -u -d -r1.583 -r1.584
--- spec.html	5 Jan 2010 11:27:22 -0000	1.583
+++ spec.html	5 Jan 2010 11:37:20 -0000	1.584
@@ -279,7 +279,7 @@
    </dl><p>This specification is available in the following formats: 
     <a href=spec.html>single page HTML</a>,
     <a href=Overview.html>multipage HTML</a>.
-This is revision 1.3584.
+This is revision 1.3587.
    </p>
    <p class=copyright><a href=http://www.w3.org/Consortium/Legal/ipr-notice#Copyright>Copyright</a>
    © 2009 <a href=http://www.w3.org/><abbr title="World Wide
@@ -3899,10 +3899,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>
 

Received on Tuesday, 5 January 2010 11:37:25 UTC