- From: poot <cvsmail@w3.org>
- Date: Fri, 17 Jun 2011 05:55:18 -0400
- To: public-html-diffs@w3.org
hixie: More notes about video.readyState. (whatwg r6178)
http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.4951&r2=1.4952&f=h
http://html5.org/tools/web-apps-tracker?from=6177&to=6178
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.4951
retrieving revision 1.4952
diff -u -d -r1.4951 -r1.4952
--- Overview.html 2 Jun 2011 23:53:50 -0000 1.4951
+++ Overview.html 2 Jun 2011 23:59:29 -0000 1.4952
@@ -23246,7 +23246,7 @@
<td>Hints to the user agent that either the author does not expect the user to need the media resource, or that the server wants to minimise unnecessary traffic.
<tr><td><dfn id="attr-media-preload-metadata" title="attr-media-preload-metadata"><code>metadata</code></dfn>
<td><dfn id="attr-media-preload-metadata-state" title="attr-media-preload-metadata-state">Metadata</dfn>
- <td>Hints to the user agent that the author does not expect the user to need the media resource, but that fetching the resource metadata (dimensions, first frame, track list, duration, etc) is reasonable.
+ <td>Hints to the user agent that the author does not expect the user to need the media resource, but that fetching the resource metadata (dimensions, first frame, track list, duration, etc) is reasonable. If the user agent precisely fetches no more than the metadata, then the <a href="#media-element">media element</a> will end up with its <code title="dom-media-readyState"><a href="#dom-media-readystate">readyState</a></code> attribute set to <code title="dom-media-HAVE_METADATA"><a href="#dom-media-have_metadata">HAVE_METADATA</a></code>; typically though, some frames will be obtained as well and it will be <code title="dom-media-HAVE_CURRENT_DATA"><a href="#dom-media-have_current_data">HAVE_CURRENT_DATA</a></code> or <code title="dom-media-HAVE_FUTURE_DATA"><a href="#dom-media-have_future_data">HAVE_FUTURE_DATA</a></code>.
<tr><td><dfn id="attr-media-preload-auto" title="attr-media-preload-auto"><code>auto</code></dfn>
<td><dfn id="attr-media-preload-auto-state" title="attr-media-preload-auto-state">Automatic</dfn>
<td>Hints to the user agent that the user agent can put the user's needs first without risk to the server, up to and including optimistically downloading the entire resource.
@@ -23613,7 +23613,12 @@
negligible. Really the only time the difference is relevant is when
painting a <code><a href="#the-video-element">video</a></code> element onto a <code><a href="#the-canvas-element">canvas</a></code>,
where it distinguishes the case where something will be drawn (<code title="dom-media-HAVE_CURRENT_DATA"><a href="#dom-media-have_current_data">HAVE_CURRENT_DATA</a></code> or
- greater) from the case where nothing is drawn (<code title="dom-media-HAVE_METADATA"><a href="#dom-media-have_metadata">HAVE_METADATA</a></code> or less).<div class="impl">
+ greater) from the case where nothing is drawn (<code title="dom-media-HAVE_METADATA"><a href="#dom-media-have_metadata">HAVE_METADATA</a></code> or less).
+ Similarly, the difference between <code title="dom-media-HAVE_CURRENT_DATA"><a href="#dom-media-have_current_data">HAVE_CURRENT_DATA</a></code> (only
+ the current frame) and <code title="dom-media-HAVE_FUTURE_DATA"><a href="#dom-media-have_future_data">HAVE_FUTURE_DATA</a></code> (at least
+ this frame and the next) can be negligible (in the extreme, only one
+ frame). The only time that distinction really matters is when a page
+ provides an interface for "frame-by-frame" navigation.<div class="impl">
<p>When the ready state of a <a href="#media-element">media element</a> whose <code title="dom-media-networkState"><a href="#dom-media-networkstate">networkState</a></code> is not <code title="dom-media-NETWORK_EMPTY"><a href="#dom-media-network_empty">NETWORK_EMPTY</a></code> changes, the
user agent must follow the steps given below:</p>
Received on Friday, 17 June 2011 09:55:19 UTC