[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 #7 from Philip Jägenstedt <philipj@opera.com> 2011-06-21 08:09:10 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?

When the position where we actually seek to is know, we just set currentTime to
that instead. Possibly currentTime should be clamped to duration synchronously
to make it a bit less weird.

It's also quite possible we have different ideas about how this would work if
currentTime were only updated asynchronously. If it is updated as soon as it is
known to which point it is possible to seek, this should be fairly fast.
However, updating it only as the seek that position has succeeded would make
the UI look sluggish.

-- 
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 08:09:12 UTC