- From: <bugzilla@jessica.w3.org>
- Date: Wed, 02 May 2012 09:00:07 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=14851 --- Comment #12 from Philip J <philipj@opera.com> 2012-05-02 09:00:06 UTC --- (In reply to comment #9) > 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. I think this makes sense now that that currentTime is stable during script execution. (When I wrote "a reference point: initialTime or currentTime" I think I meant "absolute search" vs "relative search", but that can be achieved without a flag as long as currentTime is stable.) -- 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 Wednesday, 2 May 2012 09:00:15 UTC