[Bug 14851] <video> Add seek() function for non-exact (fast) seeking

https://www.w3.org/Bugs/Public/show_bug.cgi?id=14851

--- Comment #9 from Ian 'Hixie' Hickson <ian@hixie.ch> 2012-04-30 23:06:36 UTC ---
Based on that commentary, maybe currentTime shouldn't be the approximate
version. So:

   media.currentTime = targetTime; // precise, may take seconds to complete
   media.fastSeek(targetTime); // fast, could be inaccurate

fastSeek() would also additionally ensure that if targetTime is before
currentTime, the new currentTime is also before the old currentTime, and vice
versa.

I like this proposal best of the ones so far because it is more intuitive,
API-wise. setting currentTime always sets it, it doesn't end up with some
random other value, and the operation that sets it but does so potentially
inaccurately is a method.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Monday, 30 April 2012 23:06:39 UTC