W3C home > Mailing lists > Public > public-html@w3.org > December 2008

Re: HTMLMediaElement defaultPlaybackRate and playbackRate

From: Jonas Sicking <jonas@sicking.cc>
Date: Mon, 01 Dec 2008 17:36:06 -0800
Message-ID: <49349106.9050308@sicking.cc>
To: Ian Hickson <ian@hixie.ch>
CC: Pierre-Olivier Latour <pol@apple.com>, Eric Carlson <eric.carlson@apple.com>, HTML WG <public-html@w3.org>

Ian Hickson wrote:
> On Mon, 1 Dec 2008, Pierre-Olivier Latour wrote:
>> Regarding your example UI scenario, first of all, IMHO it's enough of an 
>> edge case to be negligible against the benefits of not having both 
>> playbackRate and defaultPlaybackRate, and second of all, I just don't 
>> understand it: considering you can "bind" your UI to "playbackRate" (you 
>> both set it and observe it), and it's the same for other states, how 
>> would the 2 controllers not be in sync?
> Say that you have two controllers (e.g. the JS controller and the 
> full-screen UA-native controller). The user should be able to interact 
> with both as if they were one and the same.
> Now, consider this sequence of events:
>    1. User loads page, e.g. a presentation about penguins.
>    2. User tells the JS controller that he wants to view the video at 1.2x
>       normal speed, so that he can view the presentation faster.
>    3. The video turns out to start with a long unrelated section.
>    4. User starts fast-forwarding to the point he wants to see, using the 
>       JS controller.
>    5. User switches to full-screen.
>    6. User gets to the place he's looking for and hits "play" in the UA 
>       full-screen controller.
> The UA needs to know that the user wanted to play at 1.2x speed, not ffwd 
> speed. With defaultPlaybackRate, how can the JS controller tell the UA 
> controller what speed to use?

Is playing (rather than seeking) with a speed != 1 really common enough 
that we need to solve this use case?

I don't know that I've done that a single time in my life.

/ Jonas
Received on Tuesday, 2 December 2008 01:35:04 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:15:40 UTC