[Bug 12541] <video> Media Element seeking: the asynchronous behaviour of steps 5-12 causes unexpected, unwanted behaviour when getting the currentTime immediately after it's been set.

http://www.w3.org/Bugs/Public/show_bug.cgi?id=12541

--- Comment #8 from Rick Waldron <waldron.rick@gmail.com> 2011-06-21 15:10:40 UTC ---
(In reply to comment #6)
> You can't just set currentTime to the new value, because the new value might be
> greater than the length of the clip, and in that case you need to warp to the
> end of the clip, but you might not know that time synchronously. No?


I'm not sure how else to describe the problem that this behaviour causes...

1. Given "video" 

2. Starting at currentTime equals zero;

    video.currentTime;
    // 0

3. Set "video"s currentTime to 1 second

    video.currentTime = 1;

4. Get "video"s currentTime

    video.currentTime;
    // Could be 0, but we're expecting 1


The only browser that implements the async behaviour without additionally
implementing a means to always return the correct currentTime is Firefox 3.6 --
I'v put together the following test case:
http://dl.dropbox.com/u/3531958/12541.html which can be run in that browser to
illustrate the issue.

-- 
Configure bugmail: http://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 Tuesday, 21 June 2011 15:10:46 UTC