- From: Simon Pieters <simonp@opera.com>
- Date: Fri, 03 Jun 2011 15:31:26 +0200
On Fri, 03 Jun 2011 01:59:25 +0200, <whatwg at whatwg.org> wrote: > Author: ianh > Date: 2011-06-02 16:59:24 -0700 (Thu, 02 Jun 2011) > New Revision: 6178 > > Modified: > complete.html > index > source > Log: > [e] (0) More notes about video.readyState. > > Modified: source > =================================================================== > --- source 2011-06-02 23:53:44 UTC (rev 6177) > +++ source 2011-06-02 23:59:24 UTC (rev 6178) > @@ -30283,7 +30283,7 @@ > <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>; This is wrong if we say that the first frame is "metadata" as written a few lines above. When you have the first frame, readyState is HAVE_CURRENT_DATA. -- Simon Pieters Opera Software
Received on Friday, 3 June 2011 06:31:26 UTC