- From: poot <cvsmail@w3.org>
- Date: Fri, 30 Sep 2011 19:30:56 -0400
- To: public-html-diffs@w3.org
hixie: Define an event interface for addtrack events. (whatwg r6608)
http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.5300&r2=1.5301&f=h
http://html5.org/tools/web-apps-tracker?from=6607&to=6608
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.5300
retrieving revision 1.5301
diff -u -d -r1.5300 -r1.5301
--- Overview.html 30 Sep 2011 23:14:52 -0000 1.5300
+++ Overview.html 30 Sep 2011 23:30:44 -0000 1.5301
@@ -782,10 +782,11 @@
<li><a href="#cue-events"><span class="secno">4.8.10.12.6 </span>Event definitions</a></ol></li>
<li><a href="#user-interface"><span class="secno">4.8.10.13 </span>User interface</a></li>
<li><a href="#time-ranges"><span class="secno">4.8.10.14 </span>Time ranges</a></li>
- <li><a href="#mediaevents"><span class="secno">4.8.10.15 </span>Event summary</a></li>
- <li><a href="#security-and-privacy-considerations"><span class="secno">4.8.10.16 </span>Security and privacy considerations</a></li>
- <li><a href="#best-practices-for-authors-using-media-elements"><span class="secno">4.8.10.17 </span>Best practices for authors using media elements</a></li>
- <li><a href="#best-practices-for-implementors-of-media-elements"><span class="secno">4.8.10.18 </span>Best practices for implementors of media elements</a></ol></li>
+ <li><a href="#event-definitions"><span class="secno">4.8.10.15 </span>Event definitions</a></li>
+ <li><a href="#mediaevents"><span class="secno">4.8.10.16 </span>Event summary</a></li>
+ <li><a href="#security-and-privacy-considerations"><span class="secno">4.8.10.17 </span>Security and privacy considerations</a></li>
+ <li><a href="#best-practices-for-authors-using-media-elements"><span class="secno">4.8.10.18 </span>Best practices for authors using media elements</a></li>
+ <li><a href="#best-practices-for-implementors-of-media-elements"><span class="secno">4.8.10.19 </span>Best practices for implementors of media elements</a></ol></li>
<li><a href="#the-canvas-element"><span class="secno">4.8.11 </span>The <code>canvas</code> element</a>
<ol>
<li><a href="#color-spaces-and-color-correction"><span class="secno">4.8.11.1 </span>Color spaces and color correction</a></li>
@@ -1016,7 +1017,7 @@
<li><a href="#scroll-to-fragid"><span class="secno">5.5.9 </span>Navigating to a fragment identifier</a></li>
<li><a href="#history-traversal"><span class="secno">5.5.10 </span>History traversal</a>
<ol>
- <li><a href="#event-definitions"><span class="secno">5.5.10.1 </span>Event definitions</a></ol></li>
+ <li><a href="#event-definitions-0"><span class="secno">5.5.10.1 </span>Event definitions</a></ol></li>
<li><a href="#unloading-documents"><span class="secno">5.5.11 </span>Unloading documents</a>
<ol>
<li><a href="#event-definition"><span class="secno">5.5.11.1 </span>Event definition</a></ol></li>
@@ -27110,7 +27111,31 @@
<p>The timelines used by the objects returned by the <code title="dom-media-buffered"><a href="#dom-media-buffered">buffered</a></code>, <code title="dom-media-seekable"><a href="#dom-media-seekable">seekable</a></code> and <code title="dom-media-played"><a href="#dom-media-played">played</a></code> IDL attributes of <a href="#media-element" title="media element">media elements</a> must be that element's
<a href="#media-timeline">media timeline</a>.</p>
- </div><h5 id="mediaevents"><span class="secno">4.8.10.15 </span>Event summary</h5><p><i>This section is non-normative.</i><p>The following events fire on <a href="#media-element" title="media element">media
+ </div><h5 id="event-definitions"><span class="secno">4.8.10.15 </span>Event definitions</h5><pre class="idl">[Constructor(DOMString type, optional <a href="#trackeventinit">TrackEventInit</a> eventInitDict)]
+interface <dfn id="trackevent">TrackEvent</dfn> : <a href="#event">Event</a> {
+ readonly attribute object? <a href="#dom-trackevent-track" title="dom-TrackEvent-track">track</a>;
+};
+
+dictionary <dfn id="trackeventinit">TrackEventInit</dfn> : <a href="#eventinit">EventInit</a> {
+ object? Track;
+};</pre><dl class="domintro"><dt><var title="">event</var> . <code title="dom-TrackEvent-track"><a href="#dom-trackevent-track">track</a></code></dt>
+
+ <dd>
+
+ <p>Returns the track object (<code><a href="#texttrack">TextTrack</a></code>,
+ <code><a href="#audiotrack">AudioTrack</a></code>, or <code><a href="#videotrack">VideoTrack</a></code>) to which the
+ event relates.</p>
+
+ </dd>
+
+ </dl><div class="impl">
+
+ <p>The <dfn id="dom-trackevent-track" title="dom-TrackEvent-track"><code>track</code></dfn>
+ attribute must return the value it was initialized to. When the
+ object is created, this attribute must be initialized to null. It
+ represents the context information for the event.</p>
+
+ </div><h5 id="mediaevents"><span class="secno">4.8.10.16 </span>Event summary</h5><p><i>This section is non-normative.</i><p>The following events fire on <a href="#media-element" title="media element">media
elements</a> as part of the processing model described above:<table><thead><tr><th>Event name
<th>Interface
<th>Fired when...
@@ -27265,7 +27290,7 @@
<td>Either the <code title="dom-MediaController-volume"><a href="#dom-mediacontroller-volume">volume</a></code> attribute or the <code title="dom-MediaController-muted"><a href="#dom-mediacontroller-muted">muted</a></code> attribute has just been updated.
</table><div class="impl">
- <h5 id="security-and-privacy-considerations"><span class="secno">4.8.10.16 </span>Security and privacy considerations</h5>
+ <h5 id="security-and-privacy-considerations"><span class="secno">4.8.10.17 </span>Security and privacy considerations</h5>
<p>The main security and privacy implications of the
<code><a href="#the-video-element">video</a></code> and <code><a href="#the-audio-element">audio</a></code> elements come from the
@@ -27310,7 +27335,7 @@
for a new product, then being able to read the subtitles would
present a serious confidentiality breach.</p>
- </div><h5 id="best-practices-for-authors-using-media-elements"><span class="secno">4.8.10.17 </span>Best practices for authors using media elements</h5><p><i>This section is non-normative.</i><p>Playing audio and video resources on small devices such as
+ </div><h5 id="best-practices-for-authors-using-media-elements"><span class="secno">4.8.10.18 </span>Best practices for authors using media elements</h5><p><i>This section is non-normative.</i><p>Playing audio and video resources on small devices such as
set-top boxes or mobile phones is often constrained by limited
hardware resources in the device. For example, a device might only
support three simultaneous videos. For this reason, it is a good
@@ -27324,7 +27349,7 @@
software, or format limitations can cause video frames to be dropped
and audio to be choppy or muted.<div class="impl">
- <h5 id="best-practices-for-implementors-of-media-elements"><span class="secno">4.8.10.18 </span>Best practices for implementors of media elements</h5>
+ <h5 id="best-practices-for-implementors-of-media-elements"><span class="secno">4.8.10.19 </span>Best practices for implementors of media elements</h5>
<p><i>This section is non-normative.</i></p>
@@ -46909,7 +46934,7 @@
<a href="#dom-manipulation-task-source">DOM manipulation task source</a>.</p>
- <h5 id="event-definitions"><span class="secno">5.5.10.1 </span>Event definitions</h5>
+ <h5 id="event-definitions-0"><span class="secno">5.5.10.1 </span>Event definitions</h5>
</div><p>The <dfn id="event-popstate" title="event-popstate"><code>popstate</code></dfn> event
is fired in certain cases when navigating to a <a href="#session-history-entry">session history
Received on Friday, 30 September 2011 23:31:02 UTC