Re: [whatwg] HTML5 video seeking

2012-11-23 Thread Ian Hickson
On Mon, 14 Nov 2011, Aaron Colwell wrote: > > I was looking at the seeking algorithm and had a question about step 10. > ># 10. Wait until the user agent has established whether or not the media ># data for the new playback position is available, and, if it is, until ># it has decoded enough da

Re: [whatwg] HTML5 video seeking

2011-11-17 Thread Philip Jägenstedt
On Wed, 16 Nov 2011 19:36:26 +0100, Frank Galligan wrote: 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"

Re: [whatwg] HTML5 video seeking

2011-11-16 Thread Ralph Giles
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 15/11/11 10:32 AM, Aaron Colwell wrote: > Yeah it looks to me like starting at the requested position is the > only option. I saw the text about media engine triggered seeks, but > it seems like users would be very surprised to see the seeking & >

Re: [whatwg] HTML5 video seeking

2011-11-16 Thread Frank Galligan
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

Re: [whatwg] HTML5 video seeking

2011-11-15 Thread Chris Double
On Wed, Nov 16, 2011 at 7:19 AM, Aaron Colwell 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 requir

Re: [whatwg] HTML5 video seeking

2011-11-15 Thread Aaron Colwell
Hi Ralph, On Mon, Nov 14, 2011 at 3:58 PM, Ralph Giles wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 14/11/11 03:49 PM, Aaron Colwell wrote: > > > Does this mean the user agent must resume playback at the exact > > location specified? > > Maybe you can muck with the 'media.seek

Re: [whatwg] HTML5 video seeking

2011-11-15 Thread Aaron Colwell
Hi Philip, Thanks for the link. It took me a little while to read the whole thread. I'm not looking to support multiple styles of seeking. I was just noticing that the spec text does not appear to allow you to seek to a position different from the exact time specified. Steps 5-7 appear to bound t

Re: [whatwg] HTML5 video seeking

2011-11-15 Thread Philip Jägenstedt
On Tue, 15 Nov 2011 00:49:32 +0100, Aaron Colwell wrote: Hi, I was looking at the seeking algorithm and had a question about step 10. 10. Wait until the user agent has established whether or not the

Re: [whatwg] HTML5 video seeking

2011-11-14 Thread Simon Pieters
On Tue, 15 Nov 2011 00:49:32 +0100, Aaron Colwell wrote: Hi, I was looking at the seeking algorithm and had a question about step 10. 10. Wait until the user agent has established whether or not the

Re: [whatwg] HTML5 video seeking

2011-11-14 Thread Ralph Giles
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 14/11/11 03:49 PM, Aaron Colwell wrote: > Does this mean the user agent must resume playback at the exact > location specified? Maybe you can muck with the 'media.seekable' TimeRanges object to only show keyframes? Otherwise, it kind of sounds li

[whatwg] HTML5 video seeking

2011-11-14 Thread Aaron Colwell
Hi, I was looking at the seeking algorithm and had a question about step 10. 10. Wait until the user agent has established whether or not the media data for the new playback position is available, and, if