W3C home > Mailing lists > Public > public-html@w3.org > January 2010

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

From: Jeremy Keith <jeremy@adactio.com>
Date: Fri, 8 Jan 2010 00:19:46 +0000
Message-Id: <62379693-B103-452E-845D-B707E7AB581C@adactio.com>
To: HTMLwg WG <public-html@w3.org>
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)

Jeremy Keith

a d a c t i o

Received on Friday, 8 January 2010 00:20:21 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 9 October 2021 18:45:07 UTC