- From: Ian Hickson <ian@hixie.ch>
- Date: Tue, 10 Sep 2013 21:45:15 +0000 (UTC)
- To: Brendan Long <self@brendanlong.com>
- Cc: whatwg@whatwg.org
On Fri, 19 Jul 2013, Brendan Long wrote: > On Jul 19, 2013 3:14 PM, "Ian Hickson" <ian@hixie.ch> wrote: > > > > > > What if we added a "supportedPlaybackRates" attribute, which holds > > > an array of playback rates supported by the server, plus > > > (optionally) any rates the user agent can support due to the > > > currently buffered data (possibly requiring that the user agent have > > > enough data buffered to play at that speed for some amount of time). > > > > Wouldn't that be 0.0 .. Infinity, basically? > > I've been thinking about this more, and it seems like the buffered > attribute is enough for a JavaScript application to determine for itself > if it's safe to play faster. It does seem useful to expose the rates > supported by the server though, so an application can realize that it's > safe to play at those rates, even if there's not much buffered yet. How do browsers determine what speeds the server supports? IS that information in the protocol? I'd need to read more about this to figure out how to expose it. -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Tuesday, 10 September 2013 21:45:39 UTC