- From: Eric Carlson <eric.carlson@apple.com>
- Date: Wed, 12 Jan 2011 16:23:57 -0800
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