[Bug 13871] <video> behavior when setting currentTime to current playback position

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

--- Comment #5 from Philip Jägenstedt <philipj@opera.com> 2011-08-24 08:05:35 UTC ---
(In reply to comment #4)
> The problem is that the current behavior is not what one would expect. I do not
> expect a state exception when there is no difference in new and current
> playback position.
> 
> By my interpretation a playback position is not a *new* position unless it is
> different than the current position. As a consequence, no seek is being
> requested. So why incur an exception resulting from an erroneous attempt to
> seek to the current position?

A few reasons come to mind:

1. It's simpler to implement, as you don't have to worry about comparing a
fixed value with an ever-changing value.

2. It's more reliable for page authors, as UI won't break when one happens to
click the seek bar exactly at currentTime.

3. It's impossible to seek in any meaningful way while readyState is
HAVE_NOTHING. The sooner a page author is forced to realize this the better,
and hiding the exception for this case masks the problem.

-- 
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 Wednesday, 24 August 2011 08:05:41 UTC