[html5] r1918 - [e] (0) note case-sensitivity issues
whatwg at whatwg.org
whatwg at whatwg.org
Wed Jul 23 16:15:12 PDT 2008
Author: ianh
Date: 2008-07-23 16:15:11 -0700 (Wed, 23 Jul 2008)
New Revision: 1918
Modified:
index
source
Log:
[e] (0) note case-sensitivity issues
Modified: index
===================================================================
--- index 2008-07-23 22:30:36 UTC (rev 1917)
+++ index 2008-07-23 23:15:11 UTC (rev 1918)
@@ -2714,7 +2714,8 @@
href="http://www.w3.org/TR/REC-xml/#NT-Name"><code
title="">Name</code></a> production defined in XML, they contain no U+003A
COLON (:) characters, and they do not start with three characters "<code
- title="">xml</code>". <a href="#refsXML">[XML]</a>
+ title="">xml</code>". <a href="#refsXML">[XML]</a></p>
+ <!-- XXX case-insensitive ASCII -->
<p>The term <a href="#html-">HTML documents</a> is sometimes used in
contrast with <a href="#xml-documents">XML documents</a> to specifically
@@ -5265,12 +5266,13 @@
on getting, the DOM attribute must return the conforming value associated
with the state the attribute is in (in its canonical case), or the empty
string if the attribute is in a state that has no associated keyword
- value; and on setting, if the new value case-insensitively matches one of
- the keywords given for that attribute, then the content attribute must be
- set to the conforming value associated with the state that the attribute
- would be in if set to the given new value, otherwise, if the new value is
- the empty string, then the content attribute must be removed, otherwise,
- the setter must raise a <code>SYNTAX_ERR</code> exception.
+ value; and on setting, if the new value case-insensitively <!-- XXX -->
+ matches one of the keywords given for that attribute, then the content
+ attribute must be set to the conforming value associated with the state
+ that the attribute would be in if set to the given new value, otherwise,
+ if the new value is the empty string, then the content attribute must be
+ removed, otherwise, the setter must raise a <code>SYNTAX_ERR</code>
+ exception.
<p>If a reflecting DOM attribute is a <code>DOMString</code> but doesn't
fall into any of the above categories, then the getting and setting must
Modified: source
===================================================================
--- source 2008-07-23 22:30:36 UTC (rev 1917)
+++ source 2008-07-23 23:15:11 UTC (rev 1918)
@@ -811,7 +811,7 @@
title="">Name</code></a> production defined in XML, they contain no
U+003A COLON (:) characters, and they do not start with three
characters "<code title="">xml</code>". <a
- href="#refsXML">[XML]</a></p>
+ href="#refsXML">[XML]</a></p> <!-- XXX case-insensitive ASCII -->
<p>The term <span>HTML documents</span> is sometimes used in
contrast with <span>XML documents</span> to specifically mean
@@ -3401,12 +3401,13 @@
associated with the state the attribute is in (in its canonical
case), or the empty string if the attribute is in a state that has
no associated keyword value; and on setting, if the new value
- case-insensitively matches one of the keywords given for that
- attribute, then the content attribute must be set to the conforming
- value associated with the state that the attribute would be in if
- set to the given new value, otherwise, if the new value is the empty
- string, then the content attribute must be removed, otherwise, the
- setter must raise a <code>SYNTAX_ERR</code> exception.</p>
+ case-insensitively <!-- XXX --> matches one of the keywords given
+ for that attribute, then the content attribute must be set to the
+ conforming value associated with the state that the attribute would
+ be in if set to the given new value, otherwise, if the new value is
+ the empty string, then the content attribute must be removed,
+ otherwise, the setter must raise a <code>SYNTAX_ERR</code>
+ exception.</p>
<p>If a reflecting DOM attribute is a <code>DOMString</code> but
doesn't fall into any of the above categories, then the getting and
More information about the Commit-Watchers
mailing list