html5/spec Overview.html,1.1500,1.1501

Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv22596

Modified Files:
	Overview.html 
Log Message:
More slight reorganisation of the video section. (whatwg r2328)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1500
retrieving revision 1.1501
diff -u -d -r1.1500 -r1.1501
--- Overview.html	13 Oct 2008 21:05:33 -0000	1.1500
+++ Overview.html	13 Oct 2008 21:09:03 -0000	1.1501
@@ -14407,20 +14407,7 @@
   attribute must return a static <a href=#normalized-timeranges-object>normalized
   <code>TimeRanges</code> object</a> that represents the ranges of
   the <a href=#media-resource>media resource</a>, if any, that the user agent has so
-  far rendered, at the time the attribute is evaluated.</p><hr><p id=media-playback>When a <a href=#media-element>media element</a> is
-  <a href=#potentially-playing>potentially playing</a> and its <code>Document</code> is an
-  <a href=#active-document>active document</a>, its <a href=#current-playback-position>current playback
-  position</a> must increase monotonically at <code title=dom-media-playbackRate><a href=#dom-media-playbackrate>playbackRate</a></code> units of media
-  time per unit time of wall clock time. If this value is not 1, the
-  user agent may apply pitch adjustments to any audio component of the
-  <a href=#media-resource>media resource</a>.<p class=note>This specification doesn't define how the user agent
-  achieves the appropriate playback rate &mdash; depending on the
-  protocol and media available, it is plausible that the user agent
-  could negotiate with the server to have the server provide the media
-  data at the appropriate rate, so that (except for the period between
-  when the rate is changed and when the server updates the stream's
-  playback rate) the client doesn't actually have to drop or
-  interpolate any frames.</p><hr><p>When the <dfn id=dom-media-play title=dom-media-play><code>play()</code></dfn>
+  far rendered, at the time the attribute is evaluated.</p><hr><p>When the <dfn id=dom-media-play title=dom-media-play><code>play()</code></dfn>
   method on a <a href=#media-element>media element</a> is invoked, the user agent
   must run the following steps.<ol><li><p>If the <a href=#media-element>media element</a>'s <code title=dom-media-networkState><a href=#dom-media-networkstate>networkState</a></code> attribute has
    the value <a href=#dom-media-empty title=dom-media-EMPTY>EMPTY</a>, then the user
@@ -14489,7 +14476,20 @@
    event</a> called <code title=event-pause><a href=#event-pause>pause</a></code> at the
    element.</li>
 
-  </ol><hr><p>When the <a href=#current-playback-position>current playback position</a> of a <a href=#media-element>media
+  </ol><hr><p id=media-playback>When a <a href=#media-element>media element</a> is
+  <a href=#potentially-playing>potentially playing</a> and its <code>Document</code> is an
+  <a href=#active-document>active document</a>, its <a href=#current-playback-position>current playback
+  position</a> must increase monotonically at <code title=dom-media-playbackRate><a href=#dom-media-playbackrate>playbackRate</a></code> units of media
+  time per unit time of wall clock time. If this value is not 1, the
+  user agent may apply pitch adjustments to any audio component of the
+  <a href=#media-resource>media resource</a>.<p class=note>This specification doesn't define how the user agent
+  achieves the appropriate playback rate &mdash; depending on the
+  protocol and media available, it is plausible that the user agent
+  could negotiate with the server to have the server provide the media
+  data at the appropriate rate, so that (except for the period between
+  when the rate is changed and when the server updates the stream's
+  playback rate) the client doesn't actually have to drop or
+  interpolate any frames.</p><hr><p>When the <a href=#current-playback-position>current playback position</a> of a <a href=#media-element>media
   element</a> changes (e.g. due to playback or seeking), the user
   agent must run the following steps. If the <a href=#current-playback-position>current playback
   position</a> changes while the steps are running, then the user

Received on Monday, 13 October 2008 21:09:14 UTC