Fix #392: add missing track element events to Event Summary

PR #419

source

@@ -34660,7 +34660,7 @@ interface <dfn>MediaController</dfn> : <span>EventTarget</span> {
     fails, etc), or if <var>URL</var> is the empty string, then <span>queue a task</span> to first
     change the <span>text track readiness state</span> to <span data-x="text track failed to
     load">failed to load</span> and then <span>fire a simple event</span> named <code
-    data-x="event-error">error</code> at the <code>track</code> element. This <span
+    data-x="event-track-error">error</code> at the <code>track</code> element. This <span
     data-x="concept-task">task</span> must use the <span>DOM manipulation task source</span>. <!--
     can't be the media element one, since there might not be a media element by this point --></p>
 
@@ -34671,14 +34671,14 @@ interface <dfn>MediaController</dfn> : <span>EventTarget</span> {
     that is <span data-x="queue a task">queued</span> by the <span>networking task source</span> in
     which the aforementioned problem is found must change the <span>text track readiness
     state</span> to <span data-x="text track failed to load">failed to load</span> and <span>fire a
-    simple event</span> named <code data-x="event-error">error</code> at the <code>track</code>
+    simple event</span> named <code data-x="event-track-error">error</code> at the <code>track</code>
     element.</p>
 
     <p>If fetching does not fail, and the file was successfully processed, then the final <span
     data-x="concept-task">task</span> that is <span data-x="queue a task">queued</span> by the
     <span>networking task source</span>, after it has finished parsing the data, must change the
     <span>text track readiness state</span> to <span data-x="text track loaded">loaded</span>, and
-    <span>fire a simple event</span> named <code data-x="event-load">load</code> at the
+    <span>fire a simple event</span> named <code data-x="event-track-load">load</code> at the
     <code>track</code> element.</p>
 
     <p>If, while fetching is ongoing, either:</p>
@@ -34700,7 +34700,7 @@ interface <dfn>MediaController</dfn> : <span>EventTarget</span> {
     the URL changed), and then <span>queue a task</span> that first changes the <span>text track
     readiness state</span> to <span data-x="text track failed to load">failed to load</span> and
     then <span data-x="fire a simple event">fires a simple event</span> named <code
-    data-x="event-error">error</code> at the <code>track</code> element. This <span
+    data-x="event-track-error">error</code> at the <code>track</code> element. This <span
     data-x="concept-task">task</span> must use the <span>DOM manipulation task source</span>. <!--
     can't be the media element one, since there might not be a media element by this point --></p>
 
@@ -36451,6 +36451,38 @@ dictionary <dfn>TrackEventInit</dfn> : <span>EventInit</span> {
   </table>
 
 
+  <p>The following events fire on <code>track</code> elements:</p>
+
+  <table>
+
+   <thead>
+    <tr>
+
+     <th>Event name
+
+     <th>Interface
+
+     <th>Fired when...
+
+   <tbody>
+    <tr>
+
+     <td><dfn><code data-x="event-track-error">error</code></dfn>
+
+     <td><code>Event</code>
+
+     <td>An error occurs while fetching the track data or the type of the resource is not supported text track format.
+
+    <tr>
+
+     <td><dfn><code data-x="event-track-load">load</code></dfn>
+
+     <td><code>Event</code>
+
+     <td>A track data has been fetched and successfully processed.
+  </table>
+
+
   <p>The following events fire on <code>TextTrackCue</code> objects:</p>
 
   <table>