[html5] r6014 - [e] (0) More tweaking of the event definitions, and some additional internal not [...]

whatwg at whatwg.org whatwg at whatwg.org
Fri Apr 15 12:01:29 PDT 2011


Author: ianh
Date: 2011-04-15 12:01:27 -0700 (Fri, 15 Apr 2011)
New Revision: 6014

Modified:
   complete.html
   index
   source
Log:
[e] (0) More tweaking of the event definitions, and some additional internal notes for future fixes.

Modified: complete.html
===================================================================
--- complete.html	2011-04-15 01:10:31 UTC (rev 6013)
+++ complete.html	2011-04-15 19:01:27 UTC (rev 6014)
@@ -33085,14 +33085,6 @@
      <td><code><a href=#event>Event</a></code>
      <td>The user agent estimates that if playback were to be started now, the <a href=#media-resource>media resource</a> could be rendered at the current playback rate all the way to its end without having to stop for further buffering.
      <td><code title=dom-media-readyState><a href=#dom-media-readystate>readyState</a></code> is newly equal to <code title=dom-media-HAVE_ENOUGH_DATA><a href=#dom-media-have_enough_data>HAVE_ENOUGH_DATA</a></code>.
-    <tr><td><dfn id=event-media-waiting title=event-media-waiting><code>waiting</code></dfn>
-     <td><code><a href=#event>Event</a></code>
-     <td>Playback has stopped because the next frame is not available, but the user agent expects that frame to become available in due course.
-     <td><code title=dom-media-readyState><a href=#dom-media-readystate>readyState</a></code> is equal to or less than <code title=dom-media-HAVE_CURRENT_DATA><a href=#dom-media-have_current_data>HAVE_CURRENT_DATA</a></code>, and <code title=dom-media-paused><a href=#dom-media-paused>paused</a></code> is false. Either <code title=dom-media-seeking><a href=#dom-media-seeking>seeking</a></code> is true, or the <a href=#current-playback-position>current playback position</a> is not contained in any of the ranges in <code title=dom-media-buffered><a href=#dom-media-buffered>buffered</a></code>. It is possible for playback to stop for other reasons without <code title=dom-media-paused><a href=#dom-media-paused>paused</a></code> being false, but those reasons do not fire this event: e.g.
-<!--CONTROLLER-->
-     one of the element's <a href=#current-media-controller>current media controller</a>'s other <a href=#slaved-media-elements>slaved media elements</a> is a newly <a href=#blocked-media-element>blocked media element</a>, or
-<!--CONTROLLER-->
-     <a href=#ended-playback title="ended playback">playback ended</a>, or playback <a href=#stopped-due-to-errors>stopped due to errors</a>, or the element has <a href=#paused-for-user-interaction>paused for user interaction</a>.
     <tr><td><dfn id=event-media-playing title=event-media-playing><code>playing</code></dfn>
      <td><code><a href=#event>Event</a></code>
      <td>Playback has started after having been delayed due to lack of <a href=#media-data>media data</a>.
@@ -33101,7 +33093,15 @@
      one of the element's <a href=#current-media-controller>current media controller</a>'s other <a href=#slaved-media-elements>slaved media elements</a> was a <a href=#blocked-media-element>blocked media element</a>, or
 <!--CONTROLLER-->
      the element had been <a href=#paused-for-user-interaction>paused for user interaction</a>.
-     <!-- XXX we should consider changing that so that 'playing' fires in those two cases too (but when readyState/paused change, not when playback actually starts) -->
+     <!-- XXXXX we should change this so that 'playing' fires in those two cases too (but when readyState/paused change, not when playback actually starts) -->
+    <tr><td><dfn id=event-media-waiting title=event-media-waiting><code>waiting</code></dfn>
+     <td><code><a href=#event>Event</a></code>
+     <td>Playback has stopped because the next frame is not available, but the user agent expects that frame to become available in due course.
+     <td><code title=dom-media-readyState><a href=#dom-media-readystate>readyState</a></code> is equal to or less than <code title=dom-media-HAVE_CURRENT_DATA><a href=#dom-media-have_current_data>HAVE_CURRENT_DATA</a></code>, and <code title=dom-media-paused><a href=#dom-media-paused>paused</a></code> is false. Either <code title=dom-media-seeking><a href=#dom-media-seeking>seeking</a></code> is true, or the <a href=#current-playback-position>current playback position</a> is not contained in any of the ranges in <code title=dom-media-buffered><a href=#dom-media-buffered>buffered</a></code>. It is possible for playback to stop for other reasons without <code title=dom-media-paused><a href=#dom-media-paused>paused</a></code> being false, but those reasons do not fire this event (and when those situations resolve, a separate <code title=event-media-playing><a href=#event-media-playing>playing</a></code> event is not fired either): e.g.
+<!--CONTROLLER-->
+     one of the element's <a href=#current-media-controller>current media controller</a>'s other <a href=#slaved-media-elements>slaved media elements</a> is a newly <a href=#blocked-media-element>blocked media element</a>, or
+<!--CONTROLLER-->
+     <a href=#ended-playback title="ended playback">playback ended</a>, or playback <a href=#stopped-due-to-errors>stopped due to errors</a>, or the element has <a href=#paused-for-user-interaction>paused for user interaction</a>.
    <tbody><tr><td><dfn id=event-media-seeking title=event-media-seeking><code>seeking</code></dfn>
      <td><code><a href=#event>Event</a></code>
      <td>The <code title=dom-media-seeking><a href=#dom-media-seeking>seeking</a></code> IDL attribute changed to true and the seek operation is taking long enough that the user agent has time to fire the event.
@@ -37522,6 +37522,7 @@
   either be the empty string or the value "<code title="">1</code>".
   The attribute is used by certain user agents as an indication that
   borders should be drawn around cells of the table.</p>
+  <!--!--> <!-- http://www.w3.org/mid/BANLkTin+7AWUp0-7Jjt1+VJSa5vahJfL4w@mail.gmail.com -->
 
   <div class=impl>
   <p>Tables can be complicated to understand and navigate. To help

Modified: index
===================================================================
--- index	2011-04-15 01:10:31 UTC (rev 6013)
+++ index	2011-04-15 19:01:27 UTC (rev 6014)
@@ -33097,14 +33097,6 @@
      <td><code><a href=#event>Event</a></code>
      <td>The user agent estimates that if playback were to be started now, the <a href=#media-resource>media resource</a> could be rendered at the current playback rate all the way to its end without having to stop for further buffering.
      <td><code title=dom-media-readyState><a href=#dom-media-readystate>readyState</a></code> is newly equal to <code title=dom-media-HAVE_ENOUGH_DATA><a href=#dom-media-have_enough_data>HAVE_ENOUGH_DATA</a></code>.
-    <tr><td><dfn id=event-media-waiting title=event-media-waiting><code>waiting</code></dfn>
-     <td><code><a href=#event>Event</a></code>
-     <td>Playback has stopped because the next frame is not available, but the user agent expects that frame to become available in due course.
-     <td><code title=dom-media-readyState><a href=#dom-media-readystate>readyState</a></code> is equal to or less than <code title=dom-media-HAVE_CURRENT_DATA><a href=#dom-media-have_current_data>HAVE_CURRENT_DATA</a></code>, and <code title=dom-media-paused><a href=#dom-media-paused>paused</a></code> is false. Either <code title=dom-media-seeking><a href=#dom-media-seeking>seeking</a></code> is true, or the <a href=#current-playback-position>current playback position</a> is not contained in any of the ranges in <code title=dom-media-buffered><a href=#dom-media-buffered>buffered</a></code>. It is possible for playback to stop for other reasons without <code title=dom-media-paused><a href=#dom-media-paused>paused</a></code> being false, but those reasons do not fire this event: e.g.
-<!--CONTROLLER-->
-     one of the element's <a href=#current-media-controller>current media controller</a>'s other <a href=#slaved-media-elements>slaved media elements</a> is a newly <a href=#blocked-media-element>blocked media element</a>, or
-<!--CONTROLLER-->
-     <a href=#ended-playback title="ended playback">playback ended</a>, or playback <a href=#stopped-due-to-errors>stopped due to errors</a>, or the element has <a href=#paused-for-user-interaction>paused for user interaction</a>.
     <tr><td><dfn id=event-media-playing title=event-media-playing><code>playing</code></dfn>
      <td><code><a href=#event>Event</a></code>
      <td>Playback has started after having been delayed due to lack of <a href=#media-data>media data</a>.
@@ -33113,7 +33105,15 @@
      one of the element's <a href=#current-media-controller>current media controller</a>'s other <a href=#slaved-media-elements>slaved media elements</a> was a <a href=#blocked-media-element>blocked media element</a>, or
 <!--CONTROLLER-->
      the element had been <a href=#paused-for-user-interaction>paused for user interaction</a>.
-     <!-- XXX we should consider changing that so that 'playing' fires in those two cases too (but when readyState/paused change, not when playback actually starts) -->
+     <!-- XXXXX we should change this so that 'playing' fires in those two cases too (but when readyState/paused change, not when playback actually starts) -->
+    <tr><td><dfn id=event-media-waiting title=event-media-waiting><code>waiting</code></dfn>
+     <td><code><a href=#event>Event</a></code>
+     <td>Playback has stopped because the next frame is not available, but the user agent expects that frame to become available in due course.
+     <td><code title=dom-media-readyState><a href=#dom-media-readystate>readyState</a></code> is equal to or less than <code title=dom-media-HAVE_CURRENT_DATA><a href=#dom-media-have_current_data>HAVE_CURRENT_DATA</a></code>, and <code title=dom-media-paused><a href=#dom-media-paused>paused</a></code> is false. Either <code title=dom-media-seeking><a href=#dom-media-seeking>seeking</a></code> is true, or the <a href=#current-playback-position>current playback position</a> is not contained in any of the ranges in <code title=dom-media-buffered><a href=#dom-media-buffered>buffered</a></code>. It is possible for playback to stop for other reasons without <code title=dom-media-paused><a href=#dom-media-paused>paused</a></code> being false, but those reasons do not fire this event (and when those situations resolve, a separate <code title=event-media-playing><a href=#event-media-playing>playing</a></code> event is not fired either): e.g.
+<!--CONTROLLER-->
+     one of the element's <a href=#current-media-controller>current media controller</a>'s other <a href=#slaved-media-elements>slaved media elements</a> is a newly <a href=#blocked-media-element>blocked media element</a>, or
+<!--CONTROLLER-->
+     <a href=#ended-playback title="ended playback">playback ended</a>, or playback <a href=#stopped-due-to-errors>stopped due to errors</a>, or the element has <a href=#paused-for-user-interaction>paused for user interaction</a>.
    <tbody><tr><td><dfn id=event-media-seeking title=event-media-seeking><code>seeking</code></dfn>
      <td><code><a href=#event>Event</a></code>
      <td>The <code title=dom-media-seeking><a href=#dom-media-seeking>seeking</a></code> IDL attribute changed to true and the seek operation is taking long enough that the user agent has time to fire the event.
@@ -37534,6 +37534,7 @@
   either be the empty string or the value "<code title="">1</code>".
   The attribute is used by certain user agents as an indication that
   borders should be drawn around cells of the table.</p>
+  <!--!--> <!-- http://www.w3.org/mid/BANLkTin+7AWUp0-7Jjt1+VJSa5vahJfL4w@mail.gmail.com -->
 
   <div class=impl>
   <p>Tables can be complicated to understand and navigate. To help

Modified: source
===================================================================
--- source	2011-04-15 01:10:31 UTC (rev 6013)
+++ source	2011-04-15 19:01:27 UTC (rev 6014)
@@ -36397,15 +36397,6 @@
      <td>The user agent estimates that if playback were to be started now, the <span>media resource</span> could be rendered at the current playback rate all the way to its end without having to stop for further buffering.
      <td><code title="dom-media-readyState">readyState</code> is newly equal to <code title="dom-media-HAVE_ENOUGH_DATA">HAVE_ENOUGH_DATA</code>.
     <tr>
-     <td><dfn title="event-media-waiting"><code>waiting</code></dfn>
-     <td><code>Event</code>
-     <td>Playback has stopped because the next frame is not available, but the user agent expects that frame to become available in due course.
-     <td><code title="dom-media-readyState">readyState</code> is equal to or less than <code title="dom-media-HAVE_CURRENT_DATA">HAVE_CURRENT_DATA</code>, and <code title="dom-media-paused">paused</code> is false. Either <code title="dom-media-seeking">seeking</code> is true, or the <span>current playback position</span> is not contained in any of the ranges in <code title="dom-media-buffered">buffered</code>. It is possible for playback to stop for other reasons without <code title="dom-media-paused">paused</code> being false, but those reasons do not fire this event: e.g.
-<!--END w3c-html--><!--CONTROLLER-->
-     one of the element's <span>current media controller</span>'s other <span>slaved media elements</span> is a newly <span>blocked media element</span>, or
-<!--START w3c-html--><!--CONTROLLER-->
-     <span title="ended playback">playback ended</span>, or playback <span>stopped due to errors</span>, or the element has <span>paused for user interaction</span>.
-    <tr>
      <td><dfn title="event-media-playing"><code>playing</code></dfn>
      <td><code>Event</code>
      <td>Playback has started after having been delayed due to lack of <span>media data</span>.
@@ -36414,7 +36405,16 @@
      one of the element's <span>current media controller</span>'s other <span>slaved media elements</span> was a <span>blocked media element</span>, or
 <!--START w3c-html--><!--CONTROLLER-->
      the element had been <span>paused for user interaction</span>.
-     <!-- XXX we should consider changing that so that 'playing' fires in those two cases too (but when readyState/paused change, not when playback actually starts) -->
+     <!-- XXXXX we should change this so that 'playing' fires in those two cases too (but when readyState/paused change, not when playback actually starts) -->
+    <tr>
+     <td><dfn title="event-media-waiting"><code>waiting</code></dfn>
+     <td><code>Event</code>
+     <td>Playback has stopped because the next frame is not available, but the user agent expects that frame to become available in due course.
+     <td><code title="dom-media-readyState">readyState</code> is equal to or less than <code title="dom-media-HAVE_CURRENT_DATA">HAVE_CURRENT_DATA</code>, and <code title="dom-media-paused">paused</code> is false. Either <code title="dom-media-seeking">seeking</code> is true, or the <span>current playback position</span> is not contained in any of the ranges in <code title="dom-media-buffered">buffered</code>. It is possible for playback to stop for other reasons without <code title="dom-media-paused">paused</code> being false, but those reasons do not fire this event (and when those situations resolve, a separate <code title="event-media-playing">playing</code> event is not fired either): e.g.
+<!--END w3c-html--><!--CONTROLLER-->
+     one of the element's <span>current media controller</span>'s other <span>slaved media elements</span> is a newly <span>blocked media element</span>, or
+<!--START w3c-html--><!--CONTROLLER-->
+     <span title="ended playback">playback ended</span>, or playback <span>stopped due to errors</span>, or the element has <span>paused for user interaction</span>.
    <tbody>
     <tr>
      <td><dfn title="event-media-seeking"><code>seeking</code></dfn>
@@ -41676,6 +41676,7 @@
   either be the empty string or the value "<code title="">1</code>".
   The attribute is used by certain user agents as an indication that
   borders should be drawn around cells of the table.</p>
+  <!--!--> <!-- http://www.w3.org/mid/BANLkTin+7AWUp0-7Jjt1+VJSa5vahJfL4w@mail.gmail.com -->
 
   <div class="impl">
   <p>Tables can be complicated to understand and navigate. To help




More information about the Commit-Watchers mailing list