On Mar 17, 2011, at 12:25 AM, Ian Hickson wrote: > On Thu, 17 Mar 2011, Silvia Pfeiffer wrote: >> >> Maybe it's better to make a differentiation explicit on playbackRate, such as: >> * defaultPlaybackRate - continues to be the recommended playback rate >> for the video >> * requestedPlaybackRate - is the rate that the author/user requested >> it to be played back >> * actualPlaybackRate - is the actual rate at which the browser is >> managing to play it back (read-only) > > Something like that would work too, sure. The idea being that the author > can get information from the UA about the actual results the UA is > succeeding in providing, while the UA has the instructions from the author > (as it does today) regarding the rate it _should_ be playing at. > This would work for WebKit, where not all ports are able to determine the playback rates that are supported a priori. WebKit currently attempts to set the rate to whatever the user requests, and returns the actual playback rate for 'playbackRate'. eric
Received on Thursday, 17 March 2011 18:55:24 UTC