- From: Frank Galligan <fgalligan@google.com>
- Date: Wed, 16 Nov 2011 13:36:26 -0500
Here is another link where Ian mentions that the seek should be the exact frame. http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2008-November/017225.html This came up from 2 years ago, where I wanted to add an optional "strict" parameter to the seek call, which would default to false. Exactly the same as what Philip suggested. I'm all for it. I think Chrome added frame accurate seeking in version 7. Frank On Tue, Nov 15, 2011 at 10:37 PM, Chris Double <chris.double at double.co.nz>wrote: > On Wed, Nov 16, 2011 at 7:19 AM, Aaron Colwell <acolwell at chromium.org> > wrote: > > I'm just trying to > > determine if we are intentionally requiring frame accurate seeking at > this > > point or am I just misinterpreting some part of the spec. > > My understanding from the discussion at the time was that it was > intentionally requiring frame accurate seeking and this is what > Mozilla ended up implementing in Firefox as a result. > > Chris. > -- > http://www.bluishcoder.co.nz >
Received on Wednesday, 16 November 2011 10:36:26 UTC