[e] (0) remove orphan section (became orphaned after we removed start…

…/end/etc from <video>) git-svn-id: http://svn.whatwg.org/webapps@2436 340c8d12-0b0e-0410-8428-c7bf67bfef74
whatwg · Nov 25, 2008 · bfc7545 · bfc7545
1 parent 5cbc4fa
commit bfc7545
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 48 deletions.
diff --git a/index b/index
@@ -234,8 +234,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>
@@ -3429,17 +3428,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.</p>
-
-
-
-  <h4 id=space-separated-tokens><span class=secno>2.4.5 </span>Space-separated tokens</h4>
+  </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
@@ -5013,19 +5002,6 @@
   in base ten and then that string must be used as the new content
   attribute value.</p>
 
-  <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>
-
   <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

diff --git a/source b/source
@@ -2941,15 +2941,6 @@
   </ol>
 
 
-  <h5>Time offsets</h5>
-
-  <p class="XXX"><dfn>valid time offset</dfn>, <dfn>rules for
-  parsing time offsets</dfn>, <dfn>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.</p>
-
-
 
   <h4>Space-separated tokens</h4>
 
@@ -4860,19 +4851,6 @@
   in base ten and then that string must be used as the new content
   attribute value.</p>
 
-  <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 <span title="rules for parsing time offsets">the
-  rules for parsing time offsets</span>, 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 <span>time offset serialization
-  rules</span>, and that string must be used as the new content
-  attribute value.</p>
-
   <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