W3C home > Mailing lists > Public > public-html-commits@w3.org > June 2012

html5/spec Overview.html,1.5689,1.5690

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Fri, 15 Jun 2012 22:31:20 +0000
To: public-html-commits@w3.org
Message-Id: <E1Sff32-00082F-P4@lionel-hutz.w3.org>
Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv30863

Modified Files:
	Overview.html 
Log Message:
Allow UAs that have downloaded at least two frames of video to go into the canplaythrough mode if they aren't going to bother getting any more however long the app and user wait. (whatwg r7138)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.5689
retrieving revision 1.5690
diff -u -d -r1.5689 -r1.5690
--- Overview.html	15 Jun 2012 20:55:03 -0000	1.5689
+++ Overview.html	15 Jun 2012 22:31:16 -0000	1.5690
@@ -28081,7 +28081,7 @@
 
   <dl><dt><dfn id="dom-media-have_nothing" title="dom-media-HAVE_NOTHING"><code>HAVE_NOTHING</code></dfn> (numeric value 0)</dt>
 
-   <dd>No information regarding the <a href="#media-resource">media resource</a> is
+   <dd><p>No information regarding the <a href="#media-resource">media resource</a> is
    available. No data for the <a href="#current-playback-position">current playback position</a>
    is available. <a href="#media-element" title="media element">Media elements</a>
    whose <code title="dom-media-networkState"><a href="#dom-media-networkstate">networkState</a></code>
@@ -28091,7 +28091,7 @@
 
    <dt><dfn id="dom-media-have_metadata" title="dom-media-HAVE_METADATA"><code>HAVE_METADATA</code></dfn> (numeric value 1)</dt>
 
-   <dd>Enough of the resource has been obtained that the duration of
+   <dd><p>Enough of the resource has been obtained that the duration of
    the resource is available. In the case of a <code><a href="#the-video-element">video</a></code>
    element, the dimensions of the video are also available. The API
    will no longer throw an exception when seeking. No <a href="#media-data">media
@@ -28100,7 +28100,7 @@
 
    <dt><dfn id="dom-media-have_current_data" title="dom-media-HAVE_CURRENT_DATA"><code>HAVE_CURRENT_DATA</code></dfn> (numeric value 2)</dt>
 
-   <dd>Data for the immediate <a href="#current-playback-position">current playback position</a>
+   <dd><p>Data for the immediate <a href="#current-playback-position">current playback position</a>
    is available, but either not enough data is available that the user
    agent could successfully advance the <a href="#current-playback-position">current playback
    position</a> in the <a href="#direction-of-playback">direction of playback</a> at all
@@ -28114,7 +28114,7 @@
 
    <dt><dfn id="dom-media-have_future_data" title="dom-media-HAVE_FUTURE_DATA"><code>HAVE_FUTURE_DATA</code></dfn> (numeric value 3)</dt>
 
-   <dd>Data for the immediate <a href="#current-playback-position">current playback position</a>
+   <dd><p>Data for the immediate <a href="#current-playback-position">current playback position</a>
    is available, as well as enough data for the user agent to advance
    the <a href="#current-playback-position">current playback position</a> in the <a href="#direction-of-playback">direction
    of playback</a> at least a little without immediately reverting
@@ -28132,12 +28132,24 @@
 
    <dt><dfn id="dom-media-have_enough_data" title="dom-media-HAVE_ENOUGH_DATA"><code>HAVE_ENOUGH_DATA</code></dfn> (numeric value 4)</dt>
 
-   <dd>All the conditions described for the <code title="dom-media-HAVE_FUTURE_DATA"><a href="#dom-media-have_future_data">HAVE_FUTURE_DATA</a></code> state
-   are met, and, in addition, the user agent estimates that data is
-   being fetched at a rate where the <a href="#current-playback-position">current playback
-   position</a>, if it were to advance at the <a href="#effective-playback-rate">effective
-   playback rate</a>, would not overtake the available data before
-   playback reaches the end of the <a href="#media-resource">media resource</a>.</dd>
+   <dd>
+
+   <p>All the conditions described for the <code title="dom-media-HAVE_FUTURE_DATA"><a href="#dom-media-have_future_data">HAVE_FUTURE_DATA</a></code> state
+    are met, and, in addition, either of the following conditions is
+    also true:</p>
+
+    <ul><li>The user agent estimates that data is being fetched at a rate
+     where the <a href="#current-playback-position">current playback position</a>, if it were to
+     advance at the <a href="#effective-playback-rate">effective playback rate</a>, would not
+     overtake the available data before playback reaches the end of
+     the <a href="#media-resource">media resource</a>.</li>
+
+     <li>The user agent has entered a state where waiting longer will
+     not result in further data being obtained, and therefore nothing
+     would be gained by delaying playback any further. (For example,
+     the buffer might be full.)</li>
+
+    </ul></dd>
 
   </dl><p class="note">In practice, the difference between <code title="dom-media-HAVE_METADATA"><a href="#dom-media-have_metadata">HAVE_METADATA</a></code> and <code title="dom-media-HAVE_CURRENT_DATA"><a href="#dom-media-have_current_data">HAVE_CURRENT_DATA</a></code> is
   negligible. Really the only time the difference is relevant is when
Received on Friday, 15 June 2012 22:31:23 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 15 June 2012 22:31:26 GMT