[e] (0) Fix one case where we provide a stable state but describe it …

…oddly. Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=24484 Affected topics: DOM APIs, Video and Audio git-svn-id: http://svn.whatwg.org/webapps@8460 340c8d12-0b0e-0410-8428-c7bf67bfef74
whatwg · Feb 4, 2014 · 7a8ae7e · 7a8ae7e
1 parent fda3d6f
commit 7a8ae7e
Show file tree

Hide file tree

Showing 3 changed files with 9 additions and 18 deletions.
diff --git a/complete.html b/complete.html
@@ -27494,9 +27494,9 @@ <h5 id=playing-the-media-resource><span class=secno>4.7.10.8 </span>Playing the
   the stream's playback rate) the client doesn't actually have to drop or interpolate any
   frames.</p>
 
-  <p>Any time the user agent <a href=#provide-a-stable-state title="provide a stable state">provides a stable state</a>,
+  <p>Any time the user agent <a href=#await-a-stable-state title="await a stable state">provides a stable state</a>,
   the <a href=#official-playback-position>official playback position</a> must be set to the <a href=#current-playback-position>current playback
-  position</a>.</p>
+  position</a>.</p> <!-- cross-ref is intentionally to the other term, to help find this -->
 
   <p>When the <a href=#direction-of-playback>direction of playback</a> is backwards, any corresponding audio must be
   muted. When the <a href=#effective-playback-rate>effective playback rate</a> is so low or so high that the user agent
@@ -72021,10 +72021,7 @@ <h5 id=processing-model-4><span class=secno>7.1.4.2 </span>Processing model</h5>
   </ol><hr><p>Some of the algorithms in this specification, for historical reasons, require the user agent to
   <dfn id=pause>pause</dfn> while running a <a href=#concept-task title=concept-task>task</a> until a condition <var title="">goal</var> is met. This means running the following steps:</p>
 
-  <ol><li><p>If any asynchronously-running algorithms are <a href=#await-a-stable-state title="await a stable state">awaiting a
-   stable state</a>, then run their <a href=#synchronous-section>synchronous section</a> and then resume running
-   their asynchronous algorithm. (See the <a href=#event-loop>event loop</a> processing model definition above
-   for details.)</p>
+  <ol><li><p><a href=#provide-a-stable-state>Provide a stable state</a>.</li>
 
    <li><p>If necessary, update the rendering or user interface of any <code><a href=#document>Document</a></code> or
    <a href=#browsing-context>browsing context</a> to reflect the current state.</li>

diff --git a/index b/index
@@ -27494,9 +27494,9 @@ interface <dfn id=htmlmediaelement>HTMLMediaElement</dfn> : <a href=#htmlelement
   the stream's playback rate) the client doesn't actually have to drop or interpolate any
   frames.</p>
 
-  <p>Any time the user agent <a href=#provide-a-stable-state title="provide a stable state">provides a stable state</a>,
+  <p>Any time the user agent <a href=#await-a-stable-state title="await a stable state">provides a stable state</a>,
   the <a href=#official-playback-position>official playback position</a> must be set to the <a href=#current-playback-position>current playback
-  position</a>.</p>
+  position</a>.</p> <!-- cross-ref is intentionally to the other term, to help find this -->
 
   <p>When the <a href=#direction-of-playback>direction of playback</a> is backwards, any corresponding audio must be
   muted. When the <a href=#effective-playback-rate>effective playback rate</a> is so low or so high that the user agent
@@ -72021,10 +72021,7 @@ dictionary <dfn id=erroreventinit>ErrorEventInit</dfn> : <a href=#eventinit>Even
   </ol><hr><p>Some of the algorithms in this specification, for historical reasons, require the user agent to
   <dfn id=pause>pause</dfn> while running a <a href=#concept-task title=concept-task>task</a> until a condition <var title="">goal</var> is met. This means running the following steps:</p>
 
-  <ol><li><p>If any asynchronously-running algorithms are <a href=#await-a-stable-state title="await a stable state">awaiting a
-   stable state</a>, then run their <a href=#synchronous-section>synchronous section</a> and then resume running
-   their asynchronous algorithm. (See the <a href=#event-loop>event loop</a> processing model definition above
-   for details.)</p>
+  <ol><li><p><a href=#provide-a-stable-state>Provide a stable state</a>.</li>
 
    <li><p>If necessary, update the rendering or user interface of any <code><a href=#document>Document</a></code> or
    <a href=#browsing-context>browsing context</a> to reflect the current state.</li>

diff --git a/source b/source
@@ -29366,9 +29366,9 @@ interface <dfn>HTMLMediaElement</dfn> : <span>HTMLElement</span> {
   the stream's playback rate) the client doesn't actually have to drop or interpolate any
   frames.</p>
 
-  <p>Any time the user agent <span data-x="provide a stable state">provides a stable state</span>,
+  <p>Any time the user agent <span data-x="await a stable state">provides a stable state</span>,
   the <span>official playback position</span> must be set to the <span>current playback
-  position</span>.</p>
+  position</span>.</p> <!-- cross-ref is intentionally to the other term, to help find this -->
 
   <p>When the <span>direction of playback</span> is backwards, any corresponding audio must be
   muted. When the <span>effective playback rate</span> is so low or so high that the user agent
@@ -80462,10 +80462,7 @@ dictionary <dfn>ErrorEventInit</dfn> : <span>EventInit</span> {
 
   <ol>
 
-   <li><p>If any asynchronously-running algorithms are <span data-x="await a stable state">awaiting a
-   stable state</span>, then run their <span>synchronous section</span> and then resume running
-   their asynchronous algorithm. (See the <span>event loop</span> processing model definition above
-   for details.)</p>
+   <li><p><span>Provide a stable state</span>.</p></li>
 
    <li><p>If necessary, update the rendering or user interface of any <code>Document</code> or
    <span>browsing context</span> to reflect the current state.</p></li>