[html5] r2663 - [e] (0) grammar

[whatwg at whatwg.org]

Author: ianh
Date: 2009-01-14 00:50:40 -0800 (Wed, 14 Jan 2009)
New Revision: 2663

Modified:
   index
   source
Log:
[e] (0) grammar

Modified: index
===================================================================
--- index	2009-01-14 08:46:42 UTC (rev 2662)
+++ index	2009-01-14 08:50:40 UTC (rev 2663)
@@ -5188,19 +5188,19 @@
 
   <p>If a reflecting DOM attribute is a signed integer type
   (<code>long</code>) then, on getting, the content attribute must be
-  parsed according to <a href=#rules-for-parsing-integers title="rules for parsing integers">the
-  rules for parsing signed integers</a>, and if that is successful,
-  the resulting value must be returned. If, on the other hand, it
-  fails, or if the attribute is absent, then the default value must be
-  returned instead, or 0 if there is no default value. On setting, the
-  given value must be converted to the shortest possible string
-  representing the number as a <a href=#valid-integer>valid integer</a> in base ten
-  and then that string must be used as the new content attribute
-  value.</p>
+  parsed according to the <a href=#rules-for-parsing-integers title="rules for parsing
+  integers">rules for parsing signed integers</a>, and if that is
+  successful, the resulting value must be returned. If, on the other
+  hand, it fails, or if the attribute is absent, then the default
+  value must be returned instead, or 0 if there is no default
+  value. On setting, the given value must be converted to the shortest
+  possible string representing the number as a <a href=#valid-integer>valid
+  integer</a> in base ten and then that string must be used as the
+  new content attribute value.</p>
 
   <p>If a reflecting DOM attribute is an <em>unsigned</em> integer
   type (<code>unsigned long</code>) then, on getting, the content
-  attribute must be parsed according to <a href=#rules-for-parsing-non-negative-integers>rules for parsing
+  attribute must be parsed according to the <a href=#rules-for-parsing-non-negative-integers>rules for parsing
   non-negative integers</a>, and if that is successful, the
   resulting value must be returned. If, on the other hand, it fails,
   or if the attribute is absent, the default value must be returned
@@ -5214,7 +5214,7 @@
   (<code>unsigned long</code>) that is <dfn id=limited-to-only-positive-non-zero-numbers>limited to only positive
   non-zero numbers</dfn>, then the behavior is similar to the previous
   case, but zero is not allowed. On getting, the content attribute
-  must first be parsed according to <a href=#rules-for-parsing-non-negative-integers>rules for parsing
+  must first be parsed according to the <a href=#rules-for-parsing-non-negative-integers>rules for parsing
   non-negative integers</a>, and if that is successful, the
   resulting value must be returned. If, on the other hand, it fails,
   or if the attribute is absent, the default value must be returned
@@ -5228,15 +5228,14 @@
   <p>If a reflecting DOM attribute is a floating point number type
   (<code>float</code>) and it doesn't fall into one of the earlier
   categories, then, on getting, the content attribute must be parsed
-  according to <a href=#rules-for-parsing-floating-point-number-values title="rules for parsing floating point number
-  values">the rules for parsing floating point number values</a>,
-  and if that is successful, the resulting value must be returned. If,
-  on the other hand, it fails, or if the attribute is absent, the
-  default value must be returned instead, or 0.0 if there is no
-  default value. On setting, the given value must be converted to the
-  shortest possible string representing the number as a <a href=#valid-floating-point-number>valid
-  floating point number</a> in base ten and then that string must
-  be used as the new content attribute value.</p>
+  according to the <a href=#rules-for-parsing-floating-point-number-values>rules for parsing floating point number
+  values</a>, and if that is successful, the resulting value must
+  be returned. If, on the other hand, it fails, or if the attribute is
+  absent, the default value must be returned instead, or 0.0 if there
+  is no default value. On setting, the given value must be converted
+  to the shortest possible string representing the number as a
+  <a href=#valid-floating-point-number>valid floating point number</a> in base ten and then that
+  string must be used as the new content attribute value.</p>
 
   <p>If a reflecting DOM attribute is of the type
   <code><a href=#domtokenlist-0>DOMTokenList</a></code>, then on getting it must return a

Modified: source
===================================================================
--- source	2009-01-14 08:46:42 UTC (rev 2662)
+++ source	2009-01-14 08:50:40 UTC (rev 2663)
@@ -5012,19 +5012,19 @@
 
   <p>If a reflecting DOM attribute is a signed integer type
   (<code>long</code>) then, on getting, the content attribute must be
-  parsed according to <span title="rules for parsing integers">the
-  rules for parsing signed integers</span>, and if that is successful,
-  the resulting value must be returned. If, on the other hand, it
-  fails, or if the attribute is absent, then the default value must be
-  returned instead, or 0 if there is no default value. On setting, the
-  given value must be converted to the shortest possible string
-  representing the number as a <span>valid integer</span> in base ten
-  and then that string must be used as the new content attribute
-  value.</p>
+  parsed according to the <span title="rules for parsing
+  integers">rules for parsing signed integers</span>, and if that is
+  successful, the resulting value must be returned. If, on the other
+  hand, it fails, or if the attribute is absent, then the default
+  value must be returned instead, or 0 if there is no default
+  value. On setting, the given value must be converted to the shortest
+  possible string representing the number as a <span>valid
+  integer</span> in base ten and then that string must be used as the
+  new content attribute value.</p>
 
   <p>If a reflecting DOM attribute is an <em>unsigned</em> integer
   type (<code>unsigned long</code>) then, on getting, the content
-  attribute must be parsed according to <span>rules for parsing
+  attribute must be parsed according to the <span>rules for parsing
   non-negative integers</span>, and if that is successful, the
   resulting value must be returned. If, on the other hand, it fails,
   or if the attribute is absent, the default value must be returned
@@ -5038,7 +5038,7 @@
   (<code>unsigned long</code>) that is <dfn>limited to only positive
   non-zero numbers</dfn>, then the behavior is similar to the previous
   case, but zero is not allowed. On getting, the content attribute
-  must first be parsed according to <span>rules for parsing
+  must first be parsed according to the <span>rules for parsing
   non-negative integers</span>, and if that is successful, the
   resulting value must be returned. If, on the other hand, it fails,
   or if the attribute is absent, the default value must be returned
@@ -5052,15 +5052,14 @@
   <p>If a reflecting DOM attribute is a floating point number type
   (<code>float</code>) and it doesn't fall into one of the earlier
   categories, then, on getting, the content attribute must be parsed
-  according to <span title="rules for parsing floating point number
-  values">the rules for parsing floating point number values</span>,
-  and if that is successful, the resulting value must be returned. If,
-  on the other hand, it fails, or if the attribute is absent, the
-  default value must be returned instead, or 0.0 if there is no
-  default value. On setting, the given value must be converted to the
-  shortest possible string representing the number as a <span>valid
-  floating point number</span> in base ten and then that string must
-  be used as the new content attribute value.</p>
+  according to the <span>rules for parsing floating point number
+  values</span>, and if that is successful, the resulting value must
+  be returned. If, on the other hand, it fails, or if the attribute is
+  absent, the default value must be returned instead, or 0.0 if there
+  is no default value. On setting, the given value must be converted
+  to the shortest possible string representing the number as a
+  <span>valid floating point number</span> in base ten and then that
+  string must be used as the new content attribute value.</p>
 
   <p>If a reflecting DOM attribute is of the type
   <code>DOMTokenList</code>, then on getting it must return a