Re: Should <video> buffer control be tri-state?

On Fri, Jan 8, 2010 at 1:19 PM, Jeremy Keith <jeremy@adactio.com> wrote:

> Philip wrote:
>
>> Could you explain this a bit more, please? Isn't this what Mozilla
>>> currently does for <audio> elements that don't have an @autobuffer
>>> attribute? (i.e. "don't request any piece of the audio at all before the
>>> audio is played")
>>>
>>
>> To get the first frame and duration for Ogg Theora, you must make at least
>> 2 HTTP requests to get the beginning and end of the file (unless the
>> X-Content-Duration header is used, in which case 1 would suffice). This must
>> be done for all <audio> or <video> elements for them to reach HAVE_METADATA
>> and to fire the load event on window.
>>
>
> Gotcha. Thanks for the clarification.
>
> So, is that what Mozilla is currently doing — grabbing the headers to
> fulfil the HAVE_METADATA condition? Or simply ignoring that condition?
>
> (that question is directed not at Philip but at anyone from Mozilla who can
> help clarify this for me)


We advance to HAVE_CURRENT_DATA (first frame loaded, which for audio is
basically the same as HAVE_METADATA) before stopping the download.

Rob
-- 
"He was pierced for our transgressions, he was crushed for our iniquities;
the punishment that brought us peace was upon him, and by his wounds we are
healed. We all, like sheep, have gone astray, each of us has turned to his
own way; and the LORD has laid on him the iniquity of us all." [Isaiah
53:5-6]