W3C home > Mailing lists > Public > whatwg@whatwg.org > January 2011

[whatwg] HTML5 video: frame accuracy / SMPTE

From: Eric Carlson <eric.carlson@apple.com>
Date: Wed, 12 Jan 2011 16:23:57 -0800
Message-ID: <9E9212A7-A465-46D6-83DF-70F81118CFA1@apple.com>

On Jan 12, 2011, at 4:04 PM, Robert O'Callahan wrote:

> On Wed, Jan 12, 2011 at 9:42 PM, Philip J?genstedt <philipj at opera.com>wrote:
> 
>> For the record, this is the solution I've been imagining:
>> 
>> * add HTMLMediaElement.seek(t, [exact]), where exact defaults to false if
>> missing
>> 
>> * make setting HTMLMediaElement.currentTime be a non-exact seek, as that
>> seems to be the most common case
> 
> 
> I think setting currentTime should be exact, since a) exact seeking is
> simpler from the author's point of view and b) it would be unfortunate to
> set currentTime to value T and then discover that getting currentTime gives
> you a value other than T (assuming you're paused).
> 
  I agree that precise seeking follows the principle of least surprise, based partly on the bugs files against the <video> element on iOS where this hasn't always been the behavior.

eric
Received on Wednesday, 12 January 2011 16:23:57 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:29 UTC