[e] (0) More notes about video.readyState.

git-svn-id: http://svn.whatwg.org/webapps@6178 340c8d12-0b0e-0410-8428-c7bf67bfef74
whatwg · Jun 2, 2011 · c5eba7f · c5eba7f
1 parent 47029ca
commit c5eba7f
Show file tree

Hide file tree

Showing 3 changed files with 23 additions and 6 deletions.
diff --git a/complete.html b/complete.html
@@ -27792,7 +27792,7 @@ <h5 id=loading-the-media-resource><span class=secno>4.8.10.5 </span>Loading the
      <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.
@@ -28200,7 +28200,12 @@ <h5 id=the-ready-states><span class=secno>4.8.10.7 </span>The ready states</h5>
   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).</p>
+  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.</p>
 
   <div class=impl>
 

diff --git a/index b/index
@@ -27781,7 +27781,7 @@ interface <dfn id=htmlaudioelement>HTMLAudioElement</dfn> : <a href=#htmlmediael
      <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.
@@ -28189,7 +28189,12 @@ interface <dfn id=htmlaudioelement>HTMLAudioElement</dfn> : <a href=#htmlmediael
   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).</p>
+  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.</p>
 
   <div class=impl>
 

diff --git a/source b/source
@@ -30283,7 +30283,7 @@ interface <dfn>HTMLAudioElement</dfn> : <span>HTMLMediaElement</span> {};</pre>
     <tr>
      <td><dfn title="attr-media-preload-metadata"><code>metadata</code></dfn>
      <td><dfn 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 <span>media element</span> will end up with its <code title="dom-media-readyState">readyState</code> attribute set to <code title="dom-media-HAVE_METADATA">HAVE_METADATA</code>; typically though, some frames will be obtained as well and it will be <code title="dom-media-HAVE_CURRENT_DATA">HAVE_CURRENT_DATA</code> or <code title="dom-media-HAVE_FUTURE_DATA">HAVE_FUTURE_DATA</code>.
     <tr>
      <td><dfn title="attr-media-preload-auto"><code>auto</code></dfn>
      <td><dfn title="attr-media-preload-auto-state">Automatic</dfn>
@@ -30746,7 +30746,14 @@ interface <dfn>HTMLAudioElement</dfn> : <span>HTMLMediaElement</span> {};</pre>
   where it distinguishes the case where something will be drawn (<code
   title="dom-media-HAVE_CURRENT_DATA">HAVE_CURRENT_DATA</code> or
   greater) from the case where nothing is drawn (<code
-  title="dom-media-HAVE_METADATA">HAVE_METADATA</code> or less).</p>
+  title="dom-media-HAVE_METADATA">HAVE_METADATA</code> or less).
+  Similarly, the difference between <code
+  title="dom-media-HAVE_CURRENT_DATA">HAVE_CURRENT_DATA</code> (only
+  the current frame) and <code
+  title="dom-media-HAVE_FUTURE_DATA">HAVE_FUTURE_DATA</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.</p>
 
   <div class="impl">