[whatwg] Issue when Video currentTime used for seeking.

On Thu, Nov 13, 2008 at 10:48 PM, Biju Gm at il <bijumaillist at gmail.com> wrote:
> On Wed, Nov 12, 2008 at 3:16 AM, Chris Double <chris.double at double.co.nz> wrote:
>> On Wed, Nov 12, 2008 at 6:36 PM, Biju Gm at il <bijumaillist at gmail.com> wrote:
>>> video_element.src="http://www.double.co.nz/video_test/ascannerdarkly480.ogg";
>>> video_element.currentTime=10;
>>> video_element.play();
>> You can use:
>> v.src = "foo.ogg";
>> v.addEventListener("loadedmetadata", function() { v.currentTime=10;
>> v.play(); }, false);
> Yes we can use JS to have a work around. But there will be other problems.
> Example, the above code make all the subsequent assignment of url to
> v.src make movie start from 10th second. So again we need to add code
> to remove the event listener. That make things complicated for Web
> Developers,  (see, all Web developers I know are JSP/Java, ASP/.Net or
> Graphics Designers they all only cut and paste JavaScript code).

I still feel rather dubious about the currentTime attribute of the
video element.

When it is used to tell a server about starting at an offset rather
than a the beginning, I'd prefer we rather use media fragment URIs
(once they are standardised by the W3C media fragment working group).
It will then be obvious that the user is actually asking for a subpart
of the resource to be displayed only. This is controlled by the author
of the Web page.

When it is used to change the current play pointer during watching of
a video, i.e. is controlled by the user of the Web page, it should
really be done through an event and javascript. Maybe the onclick
event can be defined for the video element here and it could call a
seek javascript function?

I feel very dubious about mixing these two use cases into the same attribute.

Best Regards,

Received on Thursday, 13 November 2008 18:45:10 UTC