[html5] r1067 - /

whatwg at whatwg.org whatwg at whatwg.org
Thu Oct 18 16:57:02 PDT 2007


Author: ianh
Date: 2007-10-18 16:56:59 -0700 (Thu, 18 Oct 2007)
New Revision: 1067

Modified:
   index
   source
Log:
[] (0) Video: define 'reached' in terms to make cue points be better defined.

Modified: index
===================================================================
--- index	2007-10-18 10:24:06 UTC (rev 1066)
+++ index	2007-10-18 23:56:59 UTC (rev 1067)
@@ -14271,6 +14271,16 @@
    id=current>current playback position</dfn>, which must initially be zero.
    The current position is a time.
 
+  <p>When the <a href="#current">current playback position</a> is reset to a
+   specific value (e.g. when the <code title=dom-media-networkState><a
+   href="#networkstate">networkState</a></code> attribute switches to <code
+   title=dom-media-LOADED_METADATA><a
+   href="#loadedmetadata">LOADED_METADATA</a></code>, since at that time the
+   current playback position gets reset to the <a href="#effective">effective
+   start</a>), the current playback position is said to have <a
+   href="#reached" title="current playback position reaches">reached</a> that
+   value.
+
   <p>The <dfn id=currenttime
    title=dom-media-currentTime><code>currentTime</code></dfn> attribute must,
    on getting, return the <a href="#current">current playback position</a>,
@@ -14649,6 +14659,15 @@
    pitch adjustments to any audio component of the <a href="#media8">media
    resource</a>.
 
+  <p>The <a href="#current">current playback position</a> is said to have
+   <dfn id=reached title="current playback position reaches">reached</dfn> a
+   particular time whenever the current playback position changes
+   discontinuously to a new time, and whenever the <a href="#media5">media
+   element</a> is <a href="#actively">actively playing</a> and the
+   aforementioned monotonic increase of the current playback position causes
+   the current playback position to advance from before that time to exactly
+   that time or to any position after that time.
+
   <p><a href="#media8" title="media resource">Media resources</a> might be
    internally scripted or interactive. Thus, a <a href="#media5">media
    element</a> could play in a non-linear fashion. If this happens, the user
@@ -14909,7 +14928,11 @@
 
    <li>
     <p>The <a href="#current">current playback position</a> must be set to
-     the given <var title="">new playback position</var>.
+     the given <var title="">new playback position</var>. The current
+     playback position is said to have <a href="#reached" title="current
+     playback position reaches">reached</a> the time of the new position, but
+     it does not reach any of the times in between the old position and the
+     new position in the process.
 
    <li>
     <p>The <code title=dom-media-seeking><a
@@ -14969,7 +14992,8 @@
    href="#cue-point">cue point list</a>.
 
   <p>When the <a href="#current">current playback position</a> of a <a
-   href="#media5">media element</a> reaches one of the times given in the
+   href="#media5">media element</a> <a href="#reached" title="current
+   playback position reaches">reaches</a> one of the times given in the
    element's <a href="#cue-point">cue point list</a>, the user agent must
    follow these steps:
 
@@ -14982,9 +15006,13 @@
      href="#pause0">pause()</a></code> method had been invoked.
 
    <li>
-    <p>The user agent must then <a href="#firing2">fire a simple event</a>
-     called <code title=event-timeupdate><a
-     href="#timeupdate">timeupdate</a></code> at the element.
+    <p>If the time was reached through the usual monotonic increase of the
+     current playback position during normal playback, the user agent must
+     then <a href="#firing2">fire a simple event</a> called <code
+     title=event-timeupdate><a href="#timeupdate">timeupdate</a></code> at
+     the element. (In the other cases, such as explicit seeks, relevant
+     events get fired as part of the overall process of changing the current
+     playback position.)
 
    <li>
     <p>The user agent must then invoke all the non-null callbacks for all the

Modified: source
===================================================================
--- source	2007-10-18 10:24:06 UTC (rev 1066)
+++ source	2007-10-18 23:56:59 UTC (rev 1067)
@@ -12157,6 +12157,16 @@
   <dfn>current playback position</dfn>, which must initially be
   zero. The current position is a time.</p>
 
+  <p>When the <span>current playback position</span> is reset to a
+  specific value (e.g. when the <code
+  title="dom-media-networkState">networkState</code> attribute
+  switches to <code
+  title="dom-media-LOADED_METADATA">LOADED_METADATA</code>, since at
+  that time the current playback position gets reset to the
+  <span>effective start</span>), the current playback position is said
+  to have <span title="current playback position
+  reaches">reached</span> that value.</p>
+
   <p>The <dfn
   title="dom-media-currentTime"><code>currentTime</code></dfn>
   attribute must, on getting, return the <span>current playback
@@ -12504,6 +12514,15 @@
   user agent may apply pitch adjustments to any audio component of the
   <span>media resource</span>.</p>
 
+  <p>The <span>current playback position</span> is said to have <dfn
+  title="current playback position reaches">reached</dfn> a particular
+  time whenever the current playback position changes discontinuously
+  to a new time, and whenever the <span>media element</span> is
+  <span>actively playing</span> and the aforementioned monotonic
+  increase of the current playback position causes the current
+  playback position to advance from before that time to exactly that
+  time or to any position after that time.</p>
+
   <p><span title="media resource">Media resources</span> might be
   internally scripted or interactive. Thus, a <span>media
   element</span> could play in a non-linear fashion. If this happens,
@@ -12743,7 +12762,11 @@
    attribute), and abort these steps.</p></li>
 
    <li><p>The <span>current playback position</span> must be set to
-   the given <var title="">new playback position</var>.</p></li>
+   the given <var title="">new playback position</var>. The current
+   playback position is said to have <span title="current playback
+   position reaches">reached</span> the time of the new position, but
+   it does not reach any of the times in between the old position and
+   the new position in the process.</p></li>
 
    <li><p>The <code title="dom-media-seeking">seeking</code> DOM
    attribute must be set to true.</p></li>
@@ -12802,7 +12825,8 @@
   element's <span>cue point list</span>.</p>
 
   <p>When the <span>current playback position</span> of a <span>media
-  element</span> reaches one of the times given in the element's
+  element</span> <span title="current playback position
+  reaches">reaches</span> one of the times given in the element's
   <span>cue point list</span>, the user agent must follow these
   steps:</p>
 
@@ -12815,9 +12839,13 @@
    title="dom-media-pause">pause()</code> method had been
    invoked.</p></li>
 
-   <li><p>The user agent must then <span>fire a simple event</span>
-   called <code title="event-timeupdate">timeupdate</code> at the
-   element.</p></li>
+   <li><p>If the time was reached through the usual monotonic increase
+   of the current playback position during normal playback, the user
+   agent must then <span>fire a simple event</span> called <code
+   title="event-timeupdate">timeupdate</code> at the element. (In the
+   other cases, such as explicit seeks, relevant events get fired as
+   part of the overall process of changing the current playback
+   position.)</p></li>
 
    <li><p>The user agent must then invoke all the non-null callbacks
    for all the entries in the list that match the <span>current
@@ -12826,6 +12854,7 @@
 
   </ol>
 
+
   <p>Invoking a callback (an object implementing the
   <code>VoidCallback</code> interface) means calling its <code
   title="dom-VoidCallback-handleEvent">handleEvent()</code>




More information about the Commit-Watchers mailing list