- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Thu, 03 Sep 2009 11:56:39 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec In directory hutz:/tmp/cvs-serv12293 Modified Files: Overview.html Log Message: Mention that the current position is never before the earliest possible start position. (whatwg r3739) Index: Overview.html =================================================================== RCS file: /sources/public/html5/spec/Overview.html,v retrieving revision 1.2912 retrieving revision 1.2913 diff -u -d -r1.2912 -r1.2913 --- Overview.html 3 Sep 2009 11:31:52 -0000 1.2912 +++ Overview.html 3 Sep 2009 11:56:34 -0000 1.2913 @@ -19475,6 +19475,12 @@ the past 15 to 250ms, then the user agent must <a href="#queue-a-task">queue a task</a> to <a href="#fire-a-simple-event">fire a simple event</a> called <code title="event-timeupdate"><a href="#event-timeupdate">timeupdate</a></code> at the element.</p> + <p class="note">Because of the above requirement and the requirement + in the <a href="#concept-media-load-resource" title="concept-media-load-resource">resource fetch + algorithm</a> that kicks in <a href="#getting-media-metadata">when the metadata of the clip becomes + known</a>, the <a href="#current-playback-position">current playback position</a> can never be + less than the <a href="#earliest-possible-position">earliest possible position</a>.</p> + <p>User agents must act as if the timeline of the <a href="#media-resource">media resource</a> increases linearly starting from the <a href="#earliest-possible-position">earliest possible position</a>, even if the underlying <a href="#media-data">media
Received on Thursday, 3 September 2009 11:56:49 UTC