spec/Overview.html 1.1608 2436 remove orphan section (became orphaned a

remove orphan section (became orphaned after we removed start/end/etc
from <video>) (whatwg r2436)

parse a date or time string
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1608.html#parse-a-date-or-time-string
limited to only positive non-zero numbers
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1608.html#limited-to-only-positive-non-zero-numbers
2.4.5 Space-separated tokens
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1608.html#space-separated-tokens

http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html
http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.1607&r2=1.1608&f=h
http://html5.org/tools/web-apps-tracker?from=2435&to=2436

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1607
retrieving revision 1.1608
diff -u -d -r1.1607 -r1.1608
--- Overview.html 25 Nov 2008 10:46:26 -0000 1.1607
+++ Overview.html 25 Nov 2008 10:48:00 -0000 1.1608
@@ -172,8 +172,7 @@
        <li><a href=#local-dates-and-times><span class=secno>2.4.4.4 </span>Local dates and times</a></li>
        <li><a href=#global-dates-and-times><span class=secno>2.4.4.5 </span>Global dates and times</a></li>
        <li><a href=#weeks><span class=secno>2.4.4.6 </span>Weeks</a></li>
-       <li><a href=#vaguer-moments-in-time><span class=secno>2.4.4.7 </span>Vaguer moments in time</a></li>
-       <li><a href=#time-offsets><span class=secno>2.4.4.8 </span>Time offsets</a></ol></li>
+       <li><a href=#vaguer-moments-in-time><span class=secno>2.4.4.7 </span>Vaguer moments in time</a></ol></li>
      <li><a href=#space-separated-tokens><span class=secno>2.4.5 </span>Space-separated tokens</a></li>
      <li><a href=#comma-separated-tokens><span class=secno>2.4.6 </span>Comma-separated tokens</a></li>
      <li><a href=#keywords-and-enumerated-attributes><span class=secno>2.4.7 </span>Keywords and enumerated attributes</a></li>
@@ -2878,11 +2877,7 @@
 
    </li>
 
-  </ol><h5 id=time-offsets><span class=secno>2.4.4.8 </span>Time offsets</h5><p class=XXX><dfn id=valid-time-offset>valid time offset</dfn>, <dfn id=rules-for-parsing-time-offsets>rules for
-  parsing time offsets</dfn>, <dfn id=time-offset-serialization-rules>time offset serialization
-  rules</dfn>; probably in the format "5d4h3m2.1s" or similar, with
-  all components being optional, and the last component's unit suffix
-  being optional if it's in seconds.<h4 id=space-separated-tokens><span class=secno>2.4.5 </span>Space-separated tokens</h4><p>A <dfn id=set-of-space-separated-tokens>set of space-separated tokens</dfn> is a set of zero or
+  </ol><h4 id=space-separated-tokens><span class=secno>2.4.5 </span>Space-separated tokens</h4><p>A <dfn id=set-of-space-separated-tokens>set of space-separated tokens</dfn> is a set of zero or
   more words separated by one or more <a href=#space-character title="space
   character">space characters</a>, where words consist of any
   string of one or more characters, none of which are <a href=#space-character title="space character">space characters</a>.<p>A string containing a <a href=#set-of-space-separated-tokens>set of space-separated tokens</a>
@@ -4249,17 +4244,6 @@
   representing the number as a <a href=#valid-non-negative-integer>valid non-negative integer</a>
   in base ten and then that string must be used as the new content
   attribute value.<p>If a reflecting DOM attribute is a floating point number type
-  (<code>float</code>) and the content attribute is defined to contain
-  a time offset, then, on getting, the content attribute must be
-  parsed according to <a href=#rules-for-parsing-time-offsets title="rules for parsing time offsets">the
-  rules for parsing time offsets</a>, and if that is successful, the
-  resulting value, in seconds, must be returned. If that fails, or if
-  the attribute is absent, the default value must be returned, or the
-  not-a-number value (NaN) if there is no default value. On setting,
-  the given value, interpreted as a time offset in seconds, must be
-  converted to a string using the <a href=#time-offset-serialization-rules>time offset serialization
-  rules</a>, and that string must be used as the new content
-  attribute value.<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

Received on Tuesday, 25 November 2008 10:51:15 UTC