Short URL: http://html5.org/r/6080
| SVN | Bug | Comment | Time (UTC) |
|---|---|---|---|
| 6080 | 12200 | grammar | 2011-05-05 08:18 |
Index: source =================================================================== --- source (revision 6079) +++ source (revision 6080) @@ -6991,18 +6991,19 @@ attribute must set the content attribute to the specified literal value.</p> - <p>If a reflecting IDL attribute is a <code>DOMString</code> whose - content attribute is an <span>enumerated attribute</span>, and the - IDL attribute is <dfn>limited to only known values</dfn>, then, on - getting, the IDL 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, the content attribute - must be set to the specified new value.</p> + <p>If a reflecting IDL attribute is a <code>DOMString</code> + attribute whose content attribute is an <span>enumerated + attribute</span>, and the IDL attribute is <dfn>limited to only + known values</dfn>, then, on getting, the IDL 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, the + content attribute must be set to the specified new value.</p> - <p>If a reflecting IDL attribute is a <code>DOMString</code> but - doesn't fall into any of the above categories, then the getting and - setting must be done in a transparent, case-preserving manner.</p> + <p>If a reflecting IDL attribute is a <code>DOMString</code> + attribute but doesn't fall into any of the above categories, then + the getting and setting must be done in a transparent, + case-preserving manner.</p> <p>If a reflecting IDL attribute is a <code title="">boolean</code> attribute, then on getting the IDL attribute must return true if the @@ -7012,7 +7013,7 @@ set to true. (This corresponds to the rules for <span title="boolean attribute">boolean content attributes</span>.)</p> - <p>If a reflecting IDL attribute is a signed integer type + <p>If a reflecting IDL attribute has a signed integer type (<code>long</code>) then, on getting, the content attribute must be parsed according to the <span title="rules for parsing integers">rules for parsing signed integers</span>, and if that is @@ -7025,7 +7026,7 @@ a <span>valid integer</span> and then that string must be used as the new content attribute value.</p> - <p>If a reflecting IDL attribute is a signed integer type + <p>If a reflecting IDL attribute has a signed integer type (<code>long</code>) that is <dfn>limited to only non-negative numbers</dfn> then, on getting, the content attribute must be parsed according to the <span>rules for parsing non-negative @@ -7040,7 +7041,7 @@ number as a <span>valid non-negative integer</span> and then that string must be used as the new content attribute value.</p> - <p>If a reflecting IDL attribute is an <em>unsigned</em> integer + <p>If a reflecting IDL attribute has an <em>unsigned</em> integer type (<code>unsigned long</code>) then, on getting, the content attribute must be parsed according to the <span>rules for parsing non-negative integers</span>, and if that is successful, and the @@ -7057,7 +7058,7 @@ range is clamped to 2147483647 rather the normal unsigned long maximum value of 4294967295 --> - <p>If a reflecting IDL attribute is an unsigned integer type + <p>If a reflecting IDL attribute has an unsigned integer type (<code>unsigned long</code>) that is <dfn>limited to only non-negative numbers greater than zero</dfn>, then the behavior is similar to the previous case, but zero is not allowed. On getting, @@ -7074,7 +7075,7 @@ and then that string must be used as the new content attribute value.</p> <!-- see previous paragraph for note about the range --> - <p>If a reflecting IDL attribute is a floating point number type + <p>If a reflecting IDL attribute has a floating point number type (<code>double</code>), then, on getting, the content attribute must be parsed according to the <span>rules for parsing floating point number values</span>, and if that is successful, the resulting value @@ -7089,20 +7090,19 @@ throw an exception on setting, as <a href="#float-nan">defined earlier</a>.</p> - <p>If a reflecting IDL attribute is of the type + <p>If a reflecting IDL attribute has the type <code>DOMTokenList</code> or <code>DOMSettableTokenList</code>, then on getting it must return a <code>DOMTokenList</code> or <code>DOMSettableTokenList</code> object (as appropriate) whose - underlying string is the element's corresponding content - attribute. When the object mutates its underlying string, the - content attribute must itself be immediately mutated. When the - attribute is absent, then the string represented by the object is - the empty string; when the object mutates this empty string, the - user agent must add the corresponding content attribute, with its - value set to the value it would have been set to after mutating the - empty string. The same <code>DOMTokenList</code> or - <code>DOMSettableTokenList</code> object must be returned every time - for each attribute.</p> + underlying string is the element's corresponding content attribute. + When the object mutates its underlying string, the content attribute + must itself be immediately mutated. When the attribute is absent, + then the string represented by the object is the empty string; when + the object mutates this empty string, the user agent must add the + corresponding content attribute, with its value set to the value it + would have been set to after mutating the empty string. The same + <code>DOMTokenList</code> or <code>DOMSettableTokenList</code> + object must be returned every time for each attribute.</p> <div class="example">