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

[whatwg] HTML5 video seeking

From: Simon Pieters <simonp@opera.com>
Date: Tue, 15 Nov 2011 01:04:03 +0100
Message-ID: <op.v4yns1rgidj3kv@simon-pieterss-macbook.local>
On Tue, 15 Nov 2011 00:49:32 +0100, Aaron Colwell <acolwell at chromium.org>  
wrote:

> Hi,
>
> I was looking at the seeking
> algorithm<http://www.whatwg.org/specs/web-apps/current-work/multipage/the-video-element.html#seeking>
> 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 data to play back that position.
>
>
> Does this mean the user agent must resume playback at the exact location
> specified?
> What if the nearest keyframe is several seconds away?
> Is the UA expected to decode and toss the frames instead of starting
> playback at the nearest keyframe?
>
> On desktop machines I don't think this would be a problem, but on mobile
> devices it might be since the hardware may not be able to decode
> significantly faster than realtime. What is the intended behavior for  
> such
> constrained devices?
>
> Aaron

I believe this is a quality of implementation issue.

-- 
Simon Pieters
Opera Software
Received on Monday, 14 November 2011 16:04:03 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:09:09 UTC