W3C home > Mailing lists > Public > public-html-diffs@w3.org > February 2012

hixie: Fix contradiction. (whatwg r6987)

From: poot <cvsmail@w3.org>
Date: Thu, 09 Feb 2012 19:29:27 -0500
To: public-html-diffs@w3.org
Message-Id: <E1RveMh-0002kX-It@jay.w3.org>
hixie: Fix contradiction. (whatwg r6987)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.5580&r2=1.5581&f=h
http://html5.org/tools/web-apps-tracker?from=6986&to=6987

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.5580
retrieving revision 1.5581
diff -u -d -r1.5580 -r1.5581
--- Overview.html	10 Feb 2012 00:24:36 -0000	1.5580
+++ Overview.html	10 Feb 2012 00:29:19 -0000	1.5581
@@ -24323,7 +24323,7 @@
          This state does not provide a hint regarding how aggressively to actually download the media resource if buffering starts anyway (e.g. once the user hits "play").
     <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. 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 probably 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>.
+     <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, track list, duration, etc), and maybe even the first few frames, 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 probably 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>.
          When the media resource is playing, hints to the user agent that bandwidth is to be considered scarce, e.g. suggesting throttling the download so that the media data is obtained at the slowest possible rate that still maintains consistent playback.
     <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>
Received on Friday, 10 February 2012 00:29:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 10 February 2012 00:29:29 GMT