[whatwg] Author control over media preloading/buffering
Ian Hickson
ian at hixie.ch
Thu Feb 26 01:19:13 PST 2009
On Wed, 25 Feb 2009, Robert O'Callahan wrote:
>
> Under "Once enough of the media data has been fetched to determine the
> duration of the media resource, its dimensions, and other metadata",
> after setting the state to HAVE_METADATA, steps 7 and 8 say
>
> > 7. Set the element's delaying-the-load-event flag to false. This stops
> > delaying the load event.
> >
> > 8. This is the point at which a user agent that is attempting to
> > reduce network usage while still fetching the metadata for each media
> > resource would stop buffering, causing the networkState attribute to
> > switch to the NETWORK_IDLE value, if the media element did not have an
> > autobuffer or autoplay attribute.
>
> I suggested HAVE_CURRENT_DATA would be a better state for these actions,
> and I still think so. These actions should not occur until the UA is
> able to display the first frame of the video. Authors would want the
> first frame of a non-autobuffered video to be visible, and the document
> load event should fire after the first frame is available by analogy
> with images.
I've updated the note as per your suggestion.
> Is there a particular reason why you think these things should happen at
> HAVE_METADATA?
It was an oversight.
--
Ian Hickson U+1047E )\._.,--....,'``. fL
http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
More information about the whatwg
mailing list