- From: Ian Hickson <ian@hixie.ch>
- Date: Tue, 16 Jul 2013 23:45:16 +0000 (UTC)
- To: "Peter Carlson (carlsop)" <carlsop@cisco.com>
- Cc: "whatwg@whatwg.org" <whatwg@whatwg.org>
On Wed, 30 Jan 2013, Peter Carlson (carlsop) wrote: > > Problem: The problem is that the supported playback speeds of a media > element may vary per media item (e.g., an on-demand movie) and as > supported by the underlying platform. Currently the application has to > discover the supported speeds by trial and error or by an alternative > non-HTML5 method that links to the media element. > > Recommendation: We suggest that the application should be able to > discover the available speeds at which it can play the media element. > These speeds provide the allowed playbackRate values. These speeds are > provided as attributes of the media element. This seems less good than just having the browsers support all playback speeds, e.g. by decoding into a local buffer. Why would we prefer to expose the media's limitations rather than removing them? -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Tuesday, 16 July 2013 23:45:40 UTC