This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 12556 - <video> Define how currentTime is updated in terms of tasks
Summary: <video> Define how currentTime is updated in terms of tasks
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard: video async api
Keywords:
Depends on: 12267
Blocks:
  Show dependency treegraph
 
Reported: 2011-04-26 08:58 UTC by contributor
Modified: 2011-08-31 23:47 UTC (History)
7 users (show)

See Also:


Attachments

Description contributor 2011-04-26 08:58:34 UTC
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/video.html
Section: http://www.whatwg.org/specs/web-apps/current-work/#dom-media-currenttime

Comment:
Define how currentTime is updated in terms of tasks

Posted from: 83.218.67.122
User agent: Opera/9.80 (X11; Linux x86_64; U; en) Presto/2.8.131 Version/11.10
Comment 1 Philip Jägenstedt 2011-04-26 09:03:59 UTC
This is a companion bug to http://www.w3.org/Bugs/Public/show_bug.cgi?id=12267

Exactly when currentTime is updates isn't very well defined. There are basically two options:

* Let it reflect reality, which could make it be out of sync with what could be deduced from readyState and buffered. currentTime may change while a script is executing.

* Define how it is updated in terms of tasks, so that it is always consistent with the other HTMLMediaElement state and is never changed while a script is executing, except perhaps when a script seeks.

As evident from the title of this bug, I would advocate the second.

It would be very interesting to hear from the Firefox developers, since it appears they have already done something along these lines.
Comment 2 Philip Jägenstedt 2011-04-26 09:11:03 UTC
One rather serious complication is that scripts that paint to a canvas would expect that the frame they get is at the currentTime they are seeing. Currently this is simply racy, it's possible to paint a frame just before it ends and then observe the currentTime of the next frame. However, to *guarantee* that scripts always see the frame corresponding to currentTime, one would have to buffer frames from the script-seen currentTime to the actual time. This isn't really reasonable.

Leaving canvas painting racy is no worse than what we already have today, perhaps this could somehow be framed as a QoI issue, as the buffering needed isn't always feasible.
Comment 3 Ian 'Hixie' Hickson 2011-07-15 00:05:05 UTC
Marking this blocked by 12267 since it only makes sense if we fix that one first.
Comment 4 Michael[tm] Smith 2011-08-04 05:14:38 UTC
mass-move component to LC1
Comment 5 Ian 'Hixie' Hickson 2011-08-31 23:47:06 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Partially Accepted
Change Description: http://html5.org/tools/web-apps-tracker?from=6530&to=6531
Rationale: I made currentTime be fixed during script execution except for specific things that change it.