[html5] r4072 - [e] (0) changed 'fire [an event] called /event/' to 'fire [an event] named /event/'.
whatwg at whatwg.org
whatwg at whatwg.org
Sun Oct 4 04:42:00 PDT 2009
Author: ianh
Date: 2009-10-04 04:41:59 -0700 (Sun, 04 Oct 2009)
New Revision: 4072
Modified:
index
source
Log:
[e] (0) changed 'fire [an event] called /event/' to 'fire [an event] named /event/'.
Modified: index
===================================================================
--- index 2009-10-04 11:27:00 UTC (rev 4071)
+++ index 2009-10-04 11:41:59 UTC (rev 4072)
@@ -6980,7 +6980,7 @@
<a href=#xml-parser>XML parser</a>, or to the string "complete"
otherwise. Various algorithms during page loading affect this
value. When the value is set, the user agent must <a href=#fire-a-simple-event>fire a
- simple event</a> called <code title=event-readystatechange>readystatechange</code> at the
+ simple event</a> named <code title=event-readystatechange>readystatechange</code> at the
<code>Document</code> object.</p>
<p>A <code>Document</code> is said to have an <dfn id=active-parser>active
@@ -8766,7 +8766,7 @@
<p>When a user agent is to <dfn id=run-post-click-activation-steps>run post-click activation
steps</dfn> on an element, the user agent must <a href=#fire-a-simple-event>fire a simple
- event</a> called <code title=event-DOMActivate>DOMActivate</code> that is cancelable at
+ event</a> named <code title=event-DOMActivate>DOMActivate</code> that is cancelable at
that element. The default action of this event must be to <a href=#run-final-activation-steps>run
final activation steps</a> on that element. If the event is
canceled, the user agent must <a href=#run-canceled-activation-steps>run canceled activation
@@ -10579,13 +10579,13 @@
<!-- the next paragraph is similar to text in the <style> section -->
<p>The <a href=#concept-task title=concept-task>task</a> that is <a href=#queue-a-task title="queue a task">queued</a> by the <a href=#networking-task-source>networking task
source</a> once the resource has been <a href=#fetch title=fetch>fetched</a> must, if the loads were successful,
- <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple event</a> called
+ <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple event</a> named
<code title=event-load>load</code> at the <code><a href=#the-link-element>link</a></code>
element; otherwise, if the resource or one of its subresources
failed to completely load for any reason (e.g. DNS error, HTTP 404
response, a connection being prematurely closed, unsupported
Content-Type), it must instead <a href=#queue-a-task>queue a task</a> to
- <a href=#fire-a-simple-event>fire a simple event</a> called <code title=event-error>error</code> at the <code><a href=#the-link-element>link</a></code>
+ <a href=#fire-a-simple-event>fire a simple event</a> named <code title=event-error>error</code> at the <code><a href=#the-link-element>link</a></code>
element. Non-network errors in processing the resource or its
subresources (e.g. CSS parse errors, PNG decoding errors) are not
failures for the purposes of this paragraph.</p>
@@ -11764,12 +11764,12 @@
<!-- the next paragraph is similar to text in the <link> section -->
<p>Once the element has been evaluated, if it had no subresources or
once all the subresources it uses have been <a href=#fetch title=fetch>fetched</a>, the user agent must <a href=#queue-a-task>queue a
- task</a> to <a href=#fire-a-simple-event>fire a simple event</a> called <code title=event-load>load</code> at the <code><a href=#the-style-element>style</a></code> element. If
+ task</a> to <a href=#fire-a-simple-event>fire a simple event</a> named <code title=event-load>load</code> at the <code><a href=#the-style-element>style</a></code> element. If
the resource has a subresource that fails to completely load for any
reason (e.g. DNS error, HTTP 404 response, the connection being
prematurely closed, unsupported Content-Type), the user agent must
instead <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple
- event</a> called <code title=event-error>error</code> at the
+ event</a> named <code title=event-error>error</code> at the
<code><a href=#the-style-element>style</a></code> element. Non-network errors in the processing of
the element's contents or its subresources (e.g. CSS parse errors)
are not failures for the purposes of this paragraph. The
@@ -12374,7 +12374,7 @@
<dl class=switch><dt>If the load resulted in an error (for example a DNS error, or
an HTTP 404 error)</dt>
- <dd><p>Executing the script block must just consist of <a href=#fire-a-simple-event title="fire a simple event">firing a simple event</a> called
+ <dd><p>Executing the script block must just consist of <a href=#fire-a-simple-event title="fire a simple event">firing a simple event</a> named
<code title=event-error>error</code> at the element.</dd>
<dt>If the load was successful</dt>
@@ -12478,7 +12478,7 @@
<li>
- <p><a href=#fire-a-simple-event>Fire a simple event</a> called <code title=event-load>load</code> at the <code><a href=#script>script</a></code>
+ <p><a href=#fire-a-simple-event>Fire a simple event</a> named <code title=event-load>load</code> at the <code><a href=#script>script</a></code>
element.</p>
</li>
@@ -18537,7 +18537,7 @@
<dl class=switch><dt>If the download was successful and the image is <i title=img-available><a href=#img-available>available</a></i></dt>
<dd><a href=#queue-a-task>Queue a task</a> to <a href=#fire-a-simple-event>fire a simple event</a>
- called <code title=event-load>load</code> at the <code><a href=#the-img-element>img</a></code>
+ named <code title=event-load>load</code> at the <code><a href=#the-img-element>img</a></code>
element (this happens after <code title=dom-img-complete><a href=#dom-img-complete>complete</a></code> starts returning
true).</dd>
@@ -18546,7 +18546,7 @@
image)</dt>
<dd><a href=#queue-a-task>Queue a task</a> to <a href=#fire-a-simple-event>fire a simple event</a>
- called <code title=event-error>error</code> on the
+ named <code title=event-error>error</code> on the
<code><a href=#the-img-element>img</a></code> element.</dd>
</dl><p>The <a href=#task-source>task source</a> for these <a href=#concept-task title=concept-task>tasks</a> is the <a href=#dom-manipulation-task-source>DOM manipulation
@@ -19857,10 +19857,10 @@
name</a> must be set to the empty string.</p>
<p>When content loads in an <code><a href=#the-iframe-element>iframe</a></code>, after any <code title=event-load>load</code> events are fired within the content
- itself, the user agent must <a href=#fire-a-simple-event>fire a simple event</a> called
+ itself, the user agent must <a href=#fire-a-simple-event>fire a simple event</a> named
<code title=event-load>load</code> at the <code><a href=#the-iframe-element>iframe</a></code>
element. When content fails to load (e.g. due to a network error),
- then the user agent must <a href=#fire-a-simple-event>fire a simple event</a> called
+ then the user agent must <a href=#fire-a-simple-event>fire a simple event</a> named
<code title=event-error>error</code> at the element instead.</p>
<p>When there is an <a href=#active-parser>active parser</a> in the
@@ -20689,7 +20689,7 @@
<li><p>If the load failed (e.g. the <a href=#url>URL</a> could not be
<a href=#resolve-a-url title="resolve a url">resolved</a>, there was an HTTP
404 error, there was a DNS error), <a href=#fire-a-simple-event>fire a simple
- event</a> called <code title=event-error>error</code> at the
+ event</a> named <code title=event-error>error</code> at the
element, then jump to the last step in the overall set of steps
(fallback).</li>
@@ -20877,7 +20877,7 @@
<li>
<p>Once the resource is completely loaded, <a href=#queue-a-task>queue a
- task</a> to <a href=#fire-a-simple-event>fire a simple event</a> called <code title=event-load>load</code> at the element.</p>
+ task</a> to <a href=#fire-a-simple-event>fire a simple event</a> named <code title=event-load>load</code> at the element.</p>
<p>The <a href=#task-source>task source</a> for this task<!--tasks mentioned
in this section--> is the <a href=#dom-manipulation-task-source>DOM manipulation task
@@ -22123,17 +22123,17 @@
<li><p>If <var title="">aborted</var> is true, set the <code title=dom-media-error><a href=#dom-media-error>error</a></code> attribute to a new
<code><a href=#mediaerror>MediaError</a></code> object whose <code title=dom-MediaError-code><a href=#dom-mediaerror-code>code</a></code> attribute is set to <code title=dom-MediaError-MEDIA_ERR_ABORTED><a href=#dom-mediaerror-media_err_aborted>MEDIA_ERR_ABORTED</a></code>,
- <a href=#fire-a-progress-event>fire a progress event</a> called <code title=event-media-abort><a href=#event-media-abort>abort</a></code> at the <a href=#media-element>media element</a>,
+ <a href=#fire-a-progress-event>fire a progress event</a> named <code title=event-media-abort><a href=#event-media-abort>abort</a></code> at the <a href=#media-element>media element</a>,
in the context of the <a href=#fetch title=fetch>fetching process</a>
that is in progress for the element, and <a href=#fire-a-progress-event>fire a progress
- event</a> called <code title=event-media-loadend><a href=#event-media-loadend>loadend</a></code> at
+ event</a> named <code title=event-media-loadend><a href=#event-media-loadend>loadend</a></code> at
the <a href=#media-element>media element</a>, in the context of the same <a href=#fetch title=fetch>fetching process</a>.</li>
<li><p>Set the <code title=dom-media-error><a href=#dom-media-error>error</a></code> attribute
to null and the <a href=#autoplaying-flag>autoplaying flag</a> to true.</li>
<li><p>If <var title="">emptied</var> is true, <a href=#fire-a-simple-event>fire a simple
- event</a> called <code title=event-media-emptied><a href=#event-media-emptied>emptied</a></code> at
+ event</a> named <code title=event-media-emptied><a href=#event-media-emptied>emptied</a></code> at
the <a href=#media-element>media element</a>.</li>
<li><p>Invoke the <a href=#media-element>media element</a>'s <a href=#concept-media-load-algorithm title=concept-media-load-algorithm>resource selection
@@ -22190,7 +22190,7 @@
<code title=dom-media-NETWORK_LOADING><a href=#dom-media-network_loading>NETWORK_LOADING</a></code>.</li>
<li><p>⌛ <a href=#queue-a-task>Queue a task</a> to <a href=#fire-a-progress-event>fire a progress
- event</a> called <code title=event-media-loadstart><a href=#event-media-loadstart>loadstart</a></code>
+ event</a> named <code title=event-media-loadstart><a href=#event-media-loadstart>loadstart</a></code>
at the <a href=#media-element>media element</a>, with no relevant <a href=#fetch title=fetch>fetching process</a>.</li>
<li>
@@ -22228,13 +22228,13 @@
value.</li>
<li><p><a href=#queue-a-task>Queue a task</a> to <a href=#fire-a-progress-event>fire a progress
- event</a> called <code title=event-media-error><a href=#event-media-error>error</a></code> at the
+ event</a> named <code title=event-media-error><a href=#event-media-error>error</a></code> at the
<a href=#media-element>media element</a>, in the context of the <a href=#fetch title=fetch>fetching process</a> that was used to try to
obtain the <a href=#media-resource>media resource</a> in the <a href=#concept-media-load-resource title=concept-media-load-resource>resource fetch
algorithm</a>.</li>
<li><p><a href=#queue-a-task>Queue a task</a> to <a href=#fire-a-progress-event>fire a progress
- event</a> called <code title=event-media-loadend><a href=#event-media-loadend>loadend</a></code> at
+ event</a> named <code title=event-media-loadend><a href=#event-media-loadend>loadend</a></code> at
the <a href=#media-element>media element</a>, in the context of the <a href=#fetch title=fetch>fetching process</a> that was used to try to
obtain the <a href=#media-resource>media resource</a> in the <a href=#concept-media-load-resource title=concept-media-load-resource>resource fetch
algorithm</a>.</li>
@@ -22330,7 +22330,7 @@
the load failed.</li>
<li><p><i title="">Failed</i>: <a href=#queue-a-task>Queue a task</a> to
- <a href=#fire-a-simple-event>fire a simple event</a> called <code title=event-error>error</code> at the <var title="">candidate</var> element, in the context of the <a href=#fetch title=fetch>fetching process</a> that was used to try to
+ <a href=#fire-a-simple-event>fire a simple event</a> named <code title=event-error>error</code> at the <var title="">candidate</var> element, in the context of the <a href=#fetch title=fetch>fetching process</a> that was used to try to
obtain <var title="">candidate</var>'s corresponding <a href=#media-resource>media
resource</a> in the <a href=#concept-media-load-resource title=concept-media-load-resource>resource fetch
algorithm</a>.</li>
@@ -22411,13 +22411,13 @@
<p>Every 350ms (±200ms) or for every byte received, whichever
is <em>least</em> frequent, <a href=#queue-a-task>queue a task</a> to
- <a href=#fire-a-progress-event>fire a progress event</a> called <code title=event-media-progress><a href=#event-media-progress>progress</a></code> at the element, in the
+ <a href=#fire-a-progress-event>fire a progress event</a> named <code title=event-media-progress><a href=#event-media-progress>progress</a></code> at the element, in the
context of the <a href=#fetch title=fetch>fetching process</a> started
by this instance of this algorithm.</p>
<p>If at any point the user agent has received no data for more
than about three seconds, then <a href=#queue-a-task>queue a task</a> to
- <a href=#fire-a-progress-event>fire a progress event</a> called <code title=event-media-stalled><a href=#event-media-stalled>stalled</a></code> at the element, in the
+ <a href=#fire-a-progress-event>fire a progress event</a> named <code title=event-media-stalled><a href=#event-media-stalled>stalled</a></code> at the element, in the
context of the <a href=#fetch title=fetch>fetching process</a> started
by this instance of this algorithm.</p>
@@ -22435,7 +22435,7 @@
resource or not, or while waiting for user input in an interactive
resource. When a <a href=#media-element>media element</a>'s download has been
suspended, the user agent must set the <code title=dom-media-networkState><a href=#dom-media-networkstate>networkState</a></code> to <code title=dom-media-NETWORK_IDLE><a href=#dom-media-network_idle>NETWORK_IDLE</a></code> and <a href=#queue-a-task>queue
- a task</a> to <a href=#fire-a-progress-event>fire a progress event</a> called <code title=event-media-suspend><a href=#event-media-suspend>suspend</a></code> at the element, in the
+ a task</a> to <a href=#fire-a-progress-event>fire a progress event</a> named <code title=event-media-suspend><a href=#event-media-suspend>suspend</a></code> at the element, in the
context of the <a href=#fetch title=fetch>fetching process</a> started
by this instance of this algorithm. If and when downloading of the
resource resumes, the user agent must set the <code title=dom-media-networkState><a href=#dom-media-networkstate>networkState</a></code> to <code title=dom-media-NETWORK_LOADING><a href=#dom-media-network_loading>NETWORK_LOADING</a></code>.</p>
@@ -22530,7 +22530,7 @@
attribute to the duration of the resource.</p>
<p class=note>The user agent <a href=#durationChange>will</a> <a href=#queue-a-task>queue a task</a> to
- <a href=#fire-a-simple-event>fire a simple event</a> called <code title=event-media-durationchange><a href=#event-media-durationchange>durationchange</a></code> at the
+ <a href=#fire-a-simple-event>fire a simple event</a> named <code title=event-media-durationchange><a href=#event-media-durationchange>durationchange</a></code> at the
element at this point.</p>
</li>
@@ -22538,7 +22538,7 @@
<li id=fire-loadedmetadata>
<p><a href=#queue-a-task>Queue a task</a> to <a href=#fire-a-simple-event>fire a simple
- event</a> called <code title=event-media-loadedmetadata><a href=#event-media-loadedmetadata>loadedmetadata</a></code> at the
+ event</a> named <code title=event-media-loadedmetadata><a href=#event-media-loadedmetadata>loadedmetadata</a></code> at the
element.</p>
<p class=note>Before this task is run, as part of the event
@@ -22592,7 +22592,7 @@
<dd>
<p><a href=#queue-a-task>Queue a task</a> to <a href=#fire-a-progress-event>fire a progress
- event</a> called <code title=event-media-progress><a href=#event-media-progress>progress</a></code>
+ event</a> named <code title=event-media-progress><a href=#event-media-progress>progress</a></code>
at the <a href=#media-element>media element</a>, in the context of the <a href=#fetch title=fetch>fetching process</a> started by this instance
of this algorithm.</p>
@@ -22617,19 +22617,19 @@
<code title=dom-MediaError-MEDIA_ERR_NETWORK><a href=#dom-mediaerror-media_err_network>MEDIA_ERR_NETWORK</a></code>.</li>
<li><p><a href=#queue-a-task>Queue a task</a> to <a href=#fire-a-progress-event>fire a progress
- event</a> called <code title=event-media-error><a href=#event-media-error>error</a></code> at
+ event</a> named <code title=event-media-error><a href=#event-media-error>error</a></code> at
the <a href=#media-element>media element</a>, in the context of the <a href=#fetch title=fetch>fetching process</a> started by this instance
of this algorithm.</li>
<li><p><a href=#queue-a-task>Queue a task</a> to <a href=#fire-a-progress-event>fire a progress
- event</a> called <code title=event-media-loadend><a href=#event-media-loadend>loadend</a></code>
+ event</a> named <code title=event-media-loadend><a href=#event-media-loadend>loadend</a></code>
at the <a href=#media-element>media element</a>, in the context of the <a href=#fetch title=fetch>fetching process</a> started by this instance
of this algorithm.</li>
<li><p>Set the element's <code title=dom-media-networkState><a href=#dom-media-networkstate>networkState</a></code> attribute to
the <a href=#dom-media-network_empty title=dom-media-NETWORK_EMPTY>NETWORK_EMPTY</a>
value and <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple
- event</a> called <code title=event-media-emptied><a href=#event-media-emptied>emptied</a></code>
+ event</a> named <code title=event-media-emptied><a href=#event-media-emptied>emptied</a></code>
at the element.</li>
<li><p>Set the element's <a href=#delaying-the-load-event-flag>delaying-the-load-event
@@ -22659,19 +22659,19 @@
<code title=dom-MediaError-MEDIA_ERR_DECODE><a href=#dom-mediaerror-media_err_decode>MEDIA_ERR_DECODE</a></code>.</li>
<li><p><a href=#queue-a-task>Queue a task</a> to <a href=#fire-a-progress-event>fire a progress
- event</a> called <code title=event-media-error><a href=#event-media-error>error</a></code> at
+ event</a> named <code title=event-media-error><a href=#event-media-error>error</a></code> at
the <a href=#media-element>media element</a>, in the context of the <a href=#fetch title=fetch>fetching process</a> started by this instance
of this algorithm.</li>
<li><p><a href=#queue-a-task>Queue a task</a> to <a href=#fire-a-progress-event>fire a progress
- event</a> called <code title=event-media-loadend><a href=#event-media-loadend>loadend</a></code>
+ event</a> named <code title=event-media-loadend><a href=#event-media-loadend>loadend</a></code>
at the <a href=#media-element>media element</a>, in the context of the <a href=#fetch title=fetch>fetching process</a> started by this instance
of this algorithm.</li>
<li><p>Set the element's <code title=dom-media-networkState><a href=#dom-media-networkstate>networkState</a></code> attribute to
the <a href=#dom-media-network_empty title=dom-media-NETWORK_EMPTY>NETWORK_EMPTY</a>
value and <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple
- event</a> called <code title=event-media-emptied><a href=#event-media-emptied>emptied</a></code>
+ event</a> named <code title=event-media-emptied><a href=#event-media-emptied>emptied</a></code>
at the element.</li>
<li><p>Set the element's <a href=#delaying-the-load-event-flag>delaying-the-load-event
@@ -22704,12 +22704,12 @@
<code title=dom-MediaError-MEDIA_ERR_ABORT>MEDIA_ERR_ABORT</code>.</li>
<li><p><a href=#queue-a-task>Queue a task</a> to <a href=#fire-a-progress-event>fire a progress
- event</a> called <code title=event-media-abort><a href=#event-media-abort>abort</a></code> at
+ event</a> named <code title=event-media-abort><a href=#event-media-abort>abort</a></code> at
the <a href=#media-element>media element</a>, in the context of the <a href=#fetch title=fetch>fetching process</a> started by this instance
of this algorithm.</li>
<li><p><a href=#queue-a-task>Queue a task</a> to <a href=#fire-a-progress-event>fire a progress
- event</a> called <code title=event-media-loadend><a href=#event-media-loadend>loadend</a></code>
+ event</a> named <code title=event-media-loadend><a href=#event-media-loadend>loadend</a></code>
at the <a href=#media-element>media element</a>, in the context of the <a href=#fetch title=fetch>fetching process</a> started by this instance
of this algorithm.</li>
@@ -22718,7 +22718,7 @@
element's <code title=dom-media-networkState><a href=#dom-media-networkstate>networkState</a></code> attribute to
the <a href=#dom-media-network_empty title=dom-media-NETWORK_EMPTY>NETWORK_EMPTY</a>
value and <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple
- event</a> called <code title=event-media-emptied><a href=#event-media-emptied>emptied</a></code>
+ event</a> named <code title=event-media-emptied><a href=#event-media-emptied>emptied</a></code>
at the element. Otherwise, set the element's <code title=dom-media-networkState><a href=#dom-media-networkstate>networkState</a></code> attribute to
the <a href=#dom-media-network_idle title=dom-media-NETWORK_IDLE>NETWORK_IDLE</a>
value.</li>
@@ -22776,12 +22776,12 @@
<code title=dom-media-NETWORK_LOADED><a href=#dom-media-network_loaded>NETWORK_LOADED</a></code>.</li>
<li><p><a href=#queue-a-task>Queue a task</a> to <a href=#fire-a-progress-event>fire a progress
- event</a> called <code title=event-media-load><a href=#event-media-load>load</a></code> at the
+ event</a> named <code title=event-media-load><a href=#event-media-load>load</a></code> at the
<a href=#media-element>media element</a>, in the context of the <a href=#fetch title=fetch>fetching process</a> started by this instance of
this algorithm.</li>
<li><p><a href=#queue-a-task>Queue a task</a> to <a href=#fire-a-progress-event>fire a progress
- event</a> called <code title=event-media-loadend><a href=#event-media-loadend>loadend</a></code> at
+ event</a> named <code title=event-media-loadend><a href=#event-media-loadend>loadend</a></code> at
the <a href=#media-element>media element</a>, in the context of the <a href=#fetch title=fetch>fetching process</a> started by this instance of
this algorithm.</li>
@@ -22927,7 +22927,7 @@
<p id=durationChange>When the length of the <a href=#media-resource>media
resource</a> changes (e.g. from being unknown to known, or from a
previously established length to a new length) the user agent must
- <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple event</a> called
+ <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple event</a> named
<code title=event-media-durationchange><a href=#event-media-durationchange>durationchange</a></code> at the
<a href=#media-element>media element</a>.</p>
@@ -22966,7 +22966,7 @@
<a href=#earliest-possible-position>earliest possible position</a>, the user agent must <a href=#dom-media-seek title=dom-media-seek>seek</a> to the <a href=#earliest-possible-position>earliest possible
position</a>; otherwise, if the user agent has not fired a <code title=event-media-timeupdate><a href=#event-media-timeupdate>timeupdate</a></code> event at the element in
the past 15 to 250ms, then the user agent must <a href=#queue-a-task>queue a
- task</a> to <a href=#fire-a-simple-event>fire a simple event</a> called <code title=event-media-timeupdate><a href=#event-media-timeupdate>timeupdate</a></code> at the element.</p>
+ task</a> to <a href=#fire-a-simple-event>fire a simple event</a> named <code title=event-media-timeupdate><a href=#event-media-timeupdate>timeupdate</a></code> at the element.</p>
<p class=note>Because of the above requirement and the requirement
in the <a href=#concept-media-load-resource title=concept-media-load-resource>resource fetch
@@ -23107,7 +23107,7 @@
<p id=fire-loadeddata>If this is the first time this occurs for
this <a href=#media-element>media element</a> since the <code title=dom-media-load><a href=#dom-media-load>load()</a></code> algorithm was last invoked,
the user agent must <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a
- simple event</a> called <code title=event-media-loadeddata><a href=#event-media-loadeddata>loadeddata</a></code> at the element.</p>
+ simple event</a> named <code title=event-media-loadeddata><a href=#event-media-loadeddata>loadeddata</a></code> at the element.</p>
<p>If the new ready state is <code title=dom-media-HAVE_FUTURE_DATA><a href=#dom-media-have_future_data>HAVE_FUTURE_DATA</a></code> or
<code title=dom-media-HAVE_ENOUGH_DATA><a href=#dom-media-have_enough_data>HAVE_ENOUGH_DATA</a></code>,
@@ -23135,11 +23135,11 @@
<dd>
<p>The user agent must <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a
- simple event</a> called <code title=event-media-canplay><a href=#event-media-canplay>canplay</a></code>.</p>
+ simple event</a> named <code title=event-media-canplay><a href=#event-media-canplay>canplay</a></code>.</p>
<p>If the element is <a href=#potentially-playing>potentially playing</a>, the user
agent must <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple
- event</a> called <code title=event-media-playing><a href=#event-media-playing>playing</a></code>.</p>
+ event</a> named <code title=event-media-playing><a href=#event-media-playing>playing</a></code>.</p>
</dd>
@@ -23150,16 +23150,16 @@
<p>If the previous ready state was <code title=dom-media-HAVE_CURRENT_DATA><a href=#dom-media-have_current_data>HAVE_CURRENT_DATA</a></code> or
less, the user agent must <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire
- a simple event</a> called <code title=event-media-canplay><a href=#event-media-canplay>canplay</a></code>, and, if the element is also
+ a simple event</a> named <code title=event-media-canplay><a href=#event-media-canplay>canplay</a></code>, and, if the element is also
<a href=#potentially-playing>potentially playing</a>, <a href=#queue-a-task>queue a task</a> to
- <a href=#fire-a-simple-event>fire a simple event</a> called <code title=event-media-playing><a href=#event-media-playing>playing</a></code>.</p>
+ <a href=#fire-a-simple-event>fire a simple event</a> named <code title=event-media-playing><a href=#event-media-playing>playing</a></code>.</p>
<p>If the <a href=#autoplaying-flag>autoplaying flag</a> is true, and the <code title=dom-media-paused><a href=#dom-media-paused>paused</a></code> attribute is true, and the
<a href=#media-element>media element</a> has an <code title=attr-media-autoplay><a href=#attr-media-autoplay>autoplay</a></code> attribute specified,
then the user agent may also set the <code title=dom-media-paused><a href=#dom-media-paused>paused</a></code> attribute to false,
<a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple event</a>
- called <code title=event-media-play><a href=#event-media-play>play</a></code>, and <a href=#queue-a-task>queue a
- task</a> to <a href=#fire-a-simple-event>fire a simple event</a> called <code title=event-media-playing><a href=#event-media-playing>playing</a></code>.</p>
+ named <code title=event-media-play><a href=#event-media-play>play</a></code>, and <a href=#queue-a-task>queue a
+ task</a> to <a href=#fire-a-simple-event>fire a simple event</a> named <code title=event-media-playing><a href=#event-media-playing>playing</a></code>.</p>
<p class=note>User agents are not required to autoplay, and it
is suggested that user agents honor user preferences on the
@@ -23168,7 +23168,7 @@
to override the behavior if so desired.</p>
<p>In any case, the user agent must finally <a href=#queue-a-task>queue a
- task</a> to <a href=#fire-a-simple-event>fire a simple event</a> called <code title=event-media-canplaythrough><a href=#event-media-canplaythrough>canplaythrough</a></code>.</p>
+ task</a> to <a href=#fire-a-simple-event>fire a simple event</a> named <code title=event-media-canplaythrough><a href=#event-media-canplaythrough>canplaythrough</a></code>.</p>
</dd>
@@ -23438,7 +23438,7 @@
<p>When a <a href=#media-element>media element</a> that is <a href=#potentially-playing>potentially
playing</a> stops playing because it has <a href=#paused-for-user-interaction>paused for user
interaction</a>, the user agent must <a href=#queue-a-task>queue a task</a> to
- <a href=#fire-a-simple-event>fire a simple event</a> called <code title=event-media-timeupdate><a href=#event-media-timeupdate>timeupdate</a></code> at the element.</p>
+ <a href=#fire-a-simple-event>fire a simple event</a> named <code title=event-media-timeupdate><a href=#event-media-timeupdate>timeupdate</a></code> at the element.</p>
<p id=fire-waiting-when-waiting>When a <a href=#media-element>media element</a>
that is <a href=#potentially-playing>potentially playing</a> stops playing because its
@@ -23448,9 +23448,9 @@
<a href=#stopped-due-to-errors>stopped due to errors</a>, or playback having <a href=#paused-for-user-interaction>paused
for user interaction</a>, or the <a href=#dom-media-seek title=dom-media-seek>seeking algorithm</a> being invoked, the
user agent must <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple
- event</a> called <code title=event-media-timeupdate><a href=#event-media-timeupdate>timeupdate</a></code>
+ event</a> named <code title=event-media-timeupdate><a href=#event-media-timeupdate>timeupdate</a></code>
at the element, and <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple
- event</a> called <code title=event-media-waiting><a href=#event-media-waiting>waiting</a></code> at
+ event</a> named <code title=event-media-waiting><a href=#event-media-waiting>waiting</a></code> at
the element.</p>
<p>When the <a href=#current-playback-position>current playback position</a> reaches the end
@@ -23471,10 +23471,10 @@
true.</li>
<li><p>The user agent must <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire
- a simple event</a> called <code title=event-media-timeupdate><a href=#event-media-timeupdate>timeupdate</a></code> at the element.</li>
+ a simple event</a> named <code title=event-media-timeupdate><a href=#event-media-timeupdate>timeupdate</a></code> at the element.</li>
<li><p>The user agent must <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire
- a simple event</a> called <code title=event-media-ended><a href=#event-media-ended>ended</a></code>
+ a simple event</a> named <code title=event-media-ended><a href=#event-media-ended>ended</a></code>
at the element.</li>
</ol><p>When the <a href=#current-playback-position>current playback position</a> reaches the
@@ -23485,7 +23485,7 @@
<ol><li><p>Stop playback.</li>
<li><p>The user agent must <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire
- a simple event</a> called <code title=event-media-timeupdate><a href=#event-media-timeupdate>timeupdate</a></code> at the element.</li>
+ a simple event</a> named <code title=event-media-timeupdate><a href=#event-media-timeupdate>timeupdate</a></code> at the element.</li>
</ol><p>The <dfn id=dom-media-defaultplaybackrate title=dom-media-defaultPlaybackRate><code>defaultPlaybackRate</code></dfn>
attribute gives the desired speed at which the <a href=#media-resource>media
@@ -23522,7 +23522,7 @@
change value (either by being set by script or by being changed
directly by the user agent, e.g. in response to user control) the
user agent must <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple
- event</a> called <code title=event-media-ratechange><a href=#event-media-ratechange>ratechange</a></code>
+ event</a> named <code title=event-media-ratechange><a href=#event-media-ratechange>ratechange</a></code>
at the <a href=#media-element>media element</a>.</p>
<p>The <dfn id=dom-media-played title=dom-media-played><code>played</code></dfn>
@@ -23548,7 +23548,7 @@
<p class=note>This <a href=#seekUpdate>will cause</a> the user
agent to <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple
- event</a> called <code title=event-media-timeupdate><a href=#event-media-timeupdate>timeupdate</a></code> at the <a href=#media-element>media
+ event</a> named <code title=event-media-timeupdate><a href=#event-media-timeupdate>timeupdate</a></code> at the <a href=#media-element>media
element</a>.</p> <!-- if we're already playing at this point,
it might also fire 'waiting' -->
@@ -23562,21 +23562,21 @@
<ol><li><p>Change the value of <code title=dom-media-paused><a href=#dom-media-paused>paused</a></code> to false.</li>
<li><p><a href=#queue-a-task>Queue a task</a> to <a href=#fire-a-simple-event>fire a simple event</a>
- called <code title=event-media-play><a href=#event-media-play>play</a></code> at the element.</li>
+ named <code title=event-media-play><a href=#event-media-play>play</a></code> at the element.</li>
<li><p>If the <a href=#media-element>media element</a>'s <code title=dom-media-readyState><a href=#dom-media-readystate>readyState</a></code> attribute has the
value <code title=dom-media-HAVE_NOTHING><a href=#dom-media-have_nothing>HAVE_NOTHING</a></code>,
<code title=dom-media-HAVE_METADATA><a href=#dom-media-have_metadata>HAVE_METADATA</a></code>, or
<code title=dom-media-HAVE_CURRENT_DATA><a href=#dom-media-have_current_data>HAVE_CURRENT_DATA</a></code>,
<a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple event</a>
- called <code title=event-media-waiting><a href=#event-media-waiting>waiting</a></code> at the
+ named <code title=event-media-waiting><a href=#event-media-waiting>waiting</a></code> at the
element.</li>
<li><p>Otherwise, the <a href=#media-element>media element</a>'s <code title=dom-media-readyState><a href=#dom-media-readystate>readyState</a></code> attribute has the
value <code title=dom-media-HAVE_FUTURE_DATA><a href=#dom-media-have_future_data>HAVE_FUTURE_DATA</a></code> or
<code title=dom-media-HAVE_ENOUGH_DATA><a href=#dom-media-have_enough_data>HAVE_ENOUGH_DATA</a></code>;
<a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple event</a>
- called <code title=event-media-playing><a href=#event-media-playing>playing</a></code> at the
+ named <code title=event-media-playing><a href=#event-media-playing>playing</a></code> at the
element.</li>
</ol></li>
@@ -23601,11 +23601,11 @@
<ol><li><p>Change the value of <code title=dom-media-paused><a href=#dom-media-paused>paused</a></code> to true.</li>
<li><p><a href=#queue-a-task>Queue a task</a> to <a href=#fire-a-simple-event>fire a simple
- event</a> called <code title=event-media-timeupdate><a href=#event-media-timeupdate>timeupdate</a></code> at the
+ event</a> named <code title=event-media-timeupdate><a href=#event-media-timeupdate>timeupdate</a></code> at the
element.</li>
<li><p><a href=#queue-a-task>Queue a task</a> to <a href=#fire-a-simple-event>fire a simple
- event</a> called <code title=event-media-pause><a href=#event-media-pause>pause</a></code>
+ event</a> named <code title=event-media-pause><a href=#event-media-pause>pause</a></code>
at the element.</li>
</ol></li>
@@ -23678,7 +23678,7 @@
of the current playback position during normal playback, and if the
user agent has not fired a <code title=event-media-timeupdate><a href=#event-media-timeupdate>timeupdate</a></code> event at the element in
the past 15 to 250ms, then the user agent must <a href=#queue-a-task>queue a
- task</a> to <a href=#fire-a-simple-event>fire a simple event</a> called <code title=event-media-timeupdate><a href=#event-media-timeupdate>timeupdate</a></code> at the element. (In the
+ task</a> to <a href=#fire-a-simple-event>fire a simple event</a> named <code title=event-media-timeupdate><a href=#event-media-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.)</p>
@@ -23801,21 +23801,21 @@
attribute must be set to true.</li>
<li id=seekUpdate><p>The user agent must <a href=#queue-a-task>queue a
- task</a> to <a href=#fire-a-simple-event>fire a simple event</a> called <code title=event-media-timeupdate><a href=#event-media-timeupdate>timeupdate</a></code> at the element.</li>
+ task</a> to <a href=#fire-a-simple-event>fire a simple event</a> named <code title=event-media-timeupdate><a href=#event-media-timeupdate>timeupdate</a></code> at the element.</li>
<li><p>If the <a href=#media-element>media element</a> was <a href=#potentially-playing>potentially
playing</a> immediately before it started seeking, but seeking
caused its <code title=dom-media-readyState><a href=#dom-media-readystate>readyState</a></code>
attribute to change to a value lower than <code title=dom-media-HAVE_FUTURE_DATA><a href=#dom-media-have_future_data>HAVE_FUTURE_DATA</a></code>, the
user agent must <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple
- event</a> called <code title=event-media-waiting><a href=#event-media-waiting>waiting</a></code> at
+ event</a> named <code title=event-media-waiting><a href=#event-media-waiting>waiting</a></code> at
the element.</li>
<li><p>If, when it reaches this step, the user agent has still not
established whether or not the <a href=#media-data>media data</a> for the <var title="">new playback position</var> is available, and, if it is,
decoded enough data to play back that position, the user agent must
<a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple event</a>
- called <code title=event-media-seeking><a href=#event-media-seeking>seeking</a></code> at the
+ named <code title=event-media-seeking><a href=#event-media-seeking>seeking</a></code> at the
element.</li>
<li><p>If the seek was in response to a DOM method call or setting
@@ -23831,7 +23831,7 @@
attribute must be set to false.</li>
<li><p>The user agent must <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire
- a simple event</a> called <code title=event-media-seeked><a href=#event-media-seeked>seeked</a></code> at the element.</li>
+ a simple event</a> named <code title=event-media-seeked><a href=#event-media-seeked>seeked</a></code> at the element.</li>
</ol><p>The <dfn id=dom-media-seekable title=dom-media-seekable><code>seekable</code></dfn>
attribute must return a new static <a href=#normalized-timeranges-object>normalized
@@ -23957,7 +23957,7 @@
<p>Whenever either the <code title=dom-media-muted><a href=#dom-media-muted>muted</a></code> or
<code title=dom-media-volume><a href=#dom-media-volume>volume</a></code> attributes are changed,
the user agent must <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple
- event</a> called <code title=event-media-volumechange><a href=#event-media-volumechange>volumechange</a></code> at the <a href=#media-element>media
+ event</a> named <code title=event-media-volumechange><a href=#event-media-volumechange>volumechange</a></code> at the <a href=#media-element>media
element</a>.</p>
</div>
@@ -34327,7 +34327,7 @@
the element's <code title=dom-input-indeterminate><a href=#dom-input-indeterminate>indeterminate</a></code> IDL attribute
back to the values they had before the <a href=#pre-click-activation-steps>pre-click activation
steps</a> were run. The <a href=#activation-behavior>activation behavior</a> is to
- <a href=#fire-a-simple-event>fire a simple event</a> that bubbles called <code title=event-change>change</code> at the element<!-- It's not
+ <a href=#fire-a-simple-event>fire a simple event</a> that bubbles named <code title=event-change>change</code> at the element<!-- It's not
cancelable. Once this fires, the control is checked, end of
story. -->, then <a href=#broadcast-formchange-events>broadcast <code title=event-formchange>formchange</code> events</a> at the
element's <a href=#form-owner>form owner</a>.</p>
@@ -34462,7 +34462,7 @@
true. The <a href=#canceled-activation-steps>canceled activation steps</a> consist of setting
the element's <a href=#concept-fe-checked title=concept-fe-checked>checkedness</a> to
false. The <a href=#activation-behavior>activation behavior</a> is to <a href=#fire-a-simple-event>fire a
- simple event</a> that bubbles called <code title=event-change>change</code> at the element<!-- It's not
+ simple event</a> that bubbles named <code title=event-change>change</code> at the element<!-- It's not
cancelable. Once this fires, the control is checked, end of
story. -->, then <a href=#broadcast-formchange-events>broadcast <code title=event-formchange>formchange</code> events</a> at the
element's <a href=#form-owner>form owner</a>.</p>
@@ -34883,12 +34883,12 @@
<p>The <a href=#concept-task title=concept-task>task</a> that is <a href=#queue-a-task title="queue a task">queued</a> by the <a href=#networking-task-source>networking task
source</a> once the resource has been <a href=#fetch title=fetch>fetched</a>, must, if the download was successful
and the image is <i title=input-img-available><a href=#input-img-available>available</a></i>,
- <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple event</a> called
+ <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple event</a> named
<code title=event-load>load</code> at the <code><a href=#the-input-element>input</a></code>
element; and otherwise, if the fetching process fails without a
response from the remote server, or completes but the image is not a
valid or supported image, <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a
- simple event</a> called <code title=event-error>error</code> on
+ simple event</a> named <code title=event-error>error</code> on
the <code><a href=#the-input-element>input</a></code> element.</p>
<hr></div>
@@ -36058,7 +36058,7 @@
<p>When the <dfn id=event-input-input title=event-input-input><code>input</code></dfn>
event applies, any time the user causes the element's <a href=#concept-fe-value title=concept-fe-value>value</a> to change, the user agent must
<a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple event</a> that
- bubbles called <code title=event-input>input</code> at the
+ bubbles named <code title=event-input>input</code> at the
<code><a href=#the-input-element>input</a></code> element, then <a href=#broadcast-forminput-events>broadcast <code title=event-forminput>forminput</code> events</a> at the
<code><a href=#the-input-element>input</a></code> element's <a href=#form-owner>form owner</a>. User agents
may wait for a suitable break in the user's interaction before
@@ -36080,7 +36080,7 @@
action, then any time the user commits a change to the element's
<a href=#concept-fe-value title=concept-fe-value>value</a> or list of <a href=#concept-input-type-file-selected title=concept-input-type-file-selected>selected files</a>, the
user agent must <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple
- event</a> that bubbles called <code title=event-change>change</code> at the <code><a href=#the-input-element>input</a></code>
+ event</a> that bubbles named <code title=event-change>change</code> at the <code><a href=#the-input-element>input</a></code>
element, then <a href=#broadcast-formchange-events>broadcast <code title=event-formchange>formchange</code> events</a> at the
<code><a href=#the-input-element>input</a></code> element's <a href=#form-owner>form owner</a>.</p>
@@ -36104,7 +36104,7 @@
<ol><li>If the <code title=event-input-input><a href=#event-input-input>input</a></code> event
applies, <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple
- event</a> that bubbles called <code title=event-input>input</code> at the <code><a href=#the-input-element>input</a></code>
+ event</a> that bubbles named <code title=event-input>input</code> at the <code><a href=#the-input-element>input</a></code>
element.</li>
<li>If the <code title=event-input-input><a href=#event-input-input>input</a></code> event
@@ -36113,7 +36113,7 @@
<li>If the <code title=event-input-change><a href=#event-input-change>change</a></code> event
applies, <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple
- event</a> that bubbles called <code title=event-change>change</code> at the <code><a href=#the-input-element>input</a></code>
+ event</a> that bubbles named <code title=event-change>change</code> at the <code><a href=#the-input-element>input</a></code>
element.</li>
<li>If the <code title=event-input-change><a href=#event-input-change>change</a></code> event
@@ -36400,7 +36400,7 @@
<span title=event-click>click</span> event), the user agent must
set the <a href=#concept-option-selectedness title=concept-option-selectedness>selectedness</a> of the
picked <code><a href=#the-option-element>option</a></code> element to true and then <a href=#queue-a-task>queue a
- task</a> to <a href=#fire-a-simple-event>fire a simple event</a> that bubbles called
+ task</a> to <a href=#fire-a-simple-event>fire a simple event</a> that bubbles named
<code title=event-change>change</code> at the <code><a href=#the-select-element>select</a></code>
element, using the <a href=#user-interaction-task-source>user interaction task source</a> as the
task source, then <a href=#broadcast-formchange-events>broadcast <code title=event-formchange>formchange</code> events</a> at the
@@ -36436,7 +36436,7 @@
before the relevant user interaction event <!-- interaction event
spec point --> is queued (e.g. before a related <span title=event-click>click</span> event), the user agent must
<a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple event</a> that
- bubbles called <code title=event-change>change</code> at the
+ bubbles named <code title=event-change>change</code> at the
<code><a href=#the-select-element>select</a></code> element, using the <a href=#user-interaction-task-source>user interaction task
source</a> as the task source, then <a href=#broadcast-formchange-events>broadcast <code title=event-formchange>formchange</code> events</a> at the
element's <a href=#form-owner>form owner</a>.</p>
@@ -37109,7 +37109,7 @@
<p>When a <code><a href=#the-textarea-element>textarea</a></code> is <a href=#concept-textarea-mutable title=concept-textarea-mutable>mutable</a>, its <a href=#concept-textarea-raw-value title=concept-textarea-raw-value>raw value</a> should be
editable by the user. Any time the user causes the element's <a href=#concept-textarea-raw-value title=concept-textarea-raw-value>raw value</a> to change, the
user agent must <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple
- event</a> that bubbles called <code title=event-input>input</code> at the <code><a href=#the-textarea-element>textarea</a></code>
+ event</a> that bubbles named <code title=event-input>input</code> at the <code><a href=#the-textarea-element>textarea</a></code>
element, then <a href=#broadcast-forminput-events>broadcast <code title=event-forminput>forminput</code> events</a> at the
<code><a href=#the-textarea-element>textarea</a></code> element's <a href=#form-owner>form owner</a>. User agents
may wait for a suitable break in the user's interaction before
@@ -38351,7 +38351,7 @@
<p>For each element <var title="">field</var> in <var title="">invalid controls</var>, if any, in <a href=#tree-order>tree
order</a>, run the following substeps:</p>
- <ol><li><p><a href=#fire-a-simple-event>Fire a simple event</a> called <code title=event-invalid>invalid</code> that is cancelable at <var title="">field</var>.</li>
+ <ol><li><p><a href=#fire-a-simple-event>Fire a simple event</a> named <code title=event-invalid>invalid</code> that is cancelable at <var title="">field</var>.</li>
<li><p>If the event was not canceled, then add <var title="">field</var> to <var title="">unhandled invalid
controls</var>.</li>
@@ -38600,7 +38600,7 @@
</dl><p>When the <dfn id=dom-cva-checkvalidatity title=dom-cva-checkValidatity><code>checkValidity()</code></dfn>
method is invoked, if the element is a <a href=#candidate-for-constraint-validation>candidate for
constraint validation</a> and does not <a href=#concept-fv-valid title=concept-fv-valid>satisfy its constraints</a>, the user
- agent must <a href=#fire-a-simple-event>fire a simple event</a> called <code title=event-invalid>invalid</code> that is cancelable (but in this
+ agent must <a href=#fire-a-simple-event>fire a simple event</a> named <code title=event-invalid>invalid</code> that is cancelable (but in this
case has no default action) at the element and return
false. Otherwise, it must only return true without doing anything
else.</p>
@@ -38744,7 +38744,7 @@
these steps.</li>
<li><p>If the <var title="">scripted-submit</var> flag is not set,
- then <a href=#fire-a-simple-event>fire a simple event</a> that is cancelable called
+ then <a href=#fire-a-simple-event>fire a simple event</a> that is cancelable named
<code title=event-submit>submit</code>, at <var title="">form</var>. If the event's default action is prevented
(i.e. if the event is canceled) then abort these steps. Otherwise,
continue (effectively the default action is to perform the
@@ -39445,7 +39445,7 @@
<h4 id=resetting-a-form><span class=secno>4.10.18 </span>Resetting a form</h4>
<p>When a form <var title="">form</var> is <dfn id=concept-form-reset title=concept-form-reset>reset</dfn>, the user agent must
- <a href=#fire-a-simple-event>fire a simple event</a> called <code title=event-reset>reset</code>, that is cancelable, at <var title="">form</var>, and then, if that event is not canceled, must
+ <a href=#fire-a-simple-event>fire a simple event</a> named <code title=event-reset>reset</code>, that is cancelable, at <var title="">form</var>, and then, if that event is not canceled, must
invoke the <a href=#concept-form-reset-control title=concept-form-reset-control>reset
algorithm</a> of each <a href=#category-reset title=category-reset>resettable</a> elements whose <a href=#form-owner>form
owner</a> is <var title="">form</var>, and <a href=#broadcast-formchange-events>broadcast <code title=event-formchange>formchange</code> events</a> from <var title="">form</var>.</p>
@@ -39476,7 +39476,7 @@
was to <a href=#broadcast-formchange-events>broadcast <code title=event-formchange>formchange</code> events</a>; let <var title="">event name</var> be <code title=event-formchange>formchange</code>.</li>
<li><p>For each element in <var title="">controls</var>, in
- <a href=#tree-order>tree order</a>, <a href=#fire-a-simple-event>fire a simple event</a> called
+ <a href=#tree-order>tree order</a>, <a href=#fire-a-simple-event>fire a simple event</a> named
<var title="">event name</var> at the element.</li>
</ol></div>
@@ -42592,7 +42592,7 @@
<p>When an element's context menu is requested (e.g. by the user
right-clicking the element, or pressing a context menu key), the UA
- must <a href=#fire-a-simple-event>fire a simple event</a> called <code title=event-contextmenu>contextmenu</code> that bubbles and is
+ must <a href=#fire-a-simple-event>fire a simple event</a> named <code title=event-contextmenu>contextmenu</code> that bubbles and is
cancelable at the element for which the menu was requested.</p>
<p class=note>Typically, therefore, the firing of the <code title=event-contextmenu>contextmenu</code> event will be the
@@ -42607,7 +42607,7 @@
<p>If the element or one of its ancestors <em>does</em> have a
context menu assigned, then the user agent must <a href=#fire-a-simple-event>fire a simple
- event</a> called <code title=event-show>show</code> at the
+ event</a> named <code title=event-show>show</code> at the
<code><a href=#menus>menu</a></code> element of the context menu of the nearest
ancestor (including the element itself) with one assigned.</p>
<!-- v2: include modifier key information -->
@@ -48170,13 +48170,13 @@
values appropriately describing the state of the key input device at
the time the event is created.</p>
- <p><dfn id=fire-a-simple-event title="fire a simple event">Firing a simple event called
+ <p><dfn id=fire-a-simple-event title="fire a simple event">Firing a simple event named
<var title="">e</var></dfn> means that an event with the name <var title="">e</var>, with no namespace, which does not bubble (except
where otherwise stated) and is not cancelable (except where
otherwise stated), and which uses the <code>Event</code> interface,
must be dispatched at the given target.</p>
- <p><dfn id=fire-a-progress-event title="fire a progress event">Firing a progress event called
+ <p><dfn id=fire-a-progress-event title="fire a progress event">Firing a progress event named
<var title="">e</var></dfn>, optionally in the context of a
particular instance of the <a href=#fetch title=fetch>fetching
algorithm</a>, means that an event with the name <var title="">e</var>, with no namespace, which does not bubble (except
@@ -48675,7 +48675,7 @@
<li>
- <p>The user agent must <a href=#fire-a-simple-event>fire a simple event</a> called
+ <p>The user agent must <a href=#fire-a-simple-event>fire a simple event</a> named
<code title=event-beforeprint>beforeprint</code> at the
<code><a href=#window>Window</a></code> object of the <code>Document</code> that is
being printed, as well as any <a href=#nested-browsing-context title="nested browsing
@@ -48709,7 +48709,7 @@
<li>
- <p>The user agent must <a href=#fire-a-simple-event>fire a simple event</a> called
+ <p>The user agent must <a href=#fire-a-simple-event>fire a simple event</a> named
<code title=event-afterprint>afterprint</code> at the
<code><a href=#window>Window</a></code> object of the <code>Document</code> that is
being printed, as well as any <a href=#nested-browsing-context title="nested browsing
@@ -50337,7 +50337,7 @@
<li><p>If these steps were invoked with a <a href=#cache-host>cache
host</a>, and the <a href=#concept-appcache-status title=concept-appcache-status>status</a> of <var title="">cache group</var> is <i>checking</i> or
<i>downloading</i>, then <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire
- a simple event</a> called <code title=event-appcache-checking><a href=#event-appcache-checking>checking</a></code> at the
+ a simple event</a> named <code title=event-appcache-checking><a href=#event-appcache-checking>checking</a></code> at the
<code><a href=#applicationcache>ApplicationCache</a></code> singleton of that <a href=#cache-host>cache
host</a>. The default action of this event must be, if the
user agent <a href=#shows-caching-progress>shows caching progress</a>, the display of
@@ -50348,7 +50348,7 @@
<li><p>If these steps were invoked with a <a href=#cache-host>cache
host</a>, and the <a href=#concept-appcache-status title=concept-appcache-status>status</a> of <var title="">cache group</var> is <i>downloading</i>, then also
<a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple event</a>
- called <code title=event-appcache-downloading><a href=#event-appcache-downloading>downloading</a></code> that is
+ named <code title=event-appcache-downloading><a href=#event-appcache-downloading>downloading</a></code> that is
cancelable at the <code><a href=#applicationcache>ApplicationCache</a></code> singleton of that
<a href=#cache-host>cache host</a>. The default action of this event must
be, if the user agent <a href=#shows-caching-progress>shows caching progress</a>, the
@@ -50365,7 +50365,7 @@
<li><p>For each <a href=#cache-host>cache host</a> associated with an
<a href=#application-cache>application cache</a> in <var title="">cache
group</var>, <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple
- event</a> that is cancelable called <code title=event-appcache-checking><a href=#event-appcache-checking>checking</a></code> at the
+ event</a> that is cancelable named <code title=event-appcache-checking><a href=#event-appcache-checking>checking</a></code> at the
<code><a href=#applicationcache>ApplicationCache</a></code> singleton of the <a href=#cache-host>cache
host</a>. The default action of these events must be, if the
user agent <a href=#shows-caching-progress>shows caching progress</a>, the display of
@@ -50384,7 +50384,7 @@
<li><p>If this is a <a href=#concept-appcache-cache title=concept-appcache-cache>cache
attempt</a>, then this algorithm was invoked with a <a href=#cache-host>cache
host</a>; <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple
- event</a> called <code title=event-appcache-checking><a href=#event-appcache-checking>checking</a></code> that is cancelable
+ event</a> named <code title=event-appcache-checking><a href=#event-appcache-checking>checking</a></code> that is cancelable
at the <code><a href=#applicationcache>ApplicationCache</a></code> singleton of that <a href=#cache-host>cache
host</a>. The default action of this event must be, if the user
agent <a href=#shows-caching-progress>shows caching progress</a>, the display of some sort
@@ -50423,7 +50423,7 @@
<li><p>For each <a href=#cache-host>cache host</a> associated with an
<a href=#application-cache>application cache</a> in <var title="">cache
group</var>, <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple
- event</a> called <code title=event-appcache-obsolete><a href=#event-appcache-obsolete>obsolete</a></code> that is
+ event</a> named <code title=event-appcache-obsolete><a href=#event-appcache-obsolete>obsolete</a></code> that is
cancelable at the <code><a href=#applicationcache>ApplicationCache</a></code> singleton of the
<a href=#cache-host>cache host</a>. The default action of these events must
be, if the user agent <a href=#shows-caching-progress>shows caching progress</a>, the
@@ -50433,7 +50433,7 @@
<li><p>For each entry in <var title="">cache group</var>'s <a href=#concept-appcache-pending-masters title=concept-appcache-pending-masters>list of pending master
entries</a>, <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple
- event</a> that is cancelable called <code title=event-appcache-error><a href=#event-appcache-error>error</a></code> (not <code title=event-appcache-obsolete><a href=#event-appcache-obsolete>obsolete</a></code>!) at the
+ event</a> that is cancelable named <code title=event-appcache-error><a href=#event-appcache-error>error</a></code> (not <code title=event-appcache-obsolete><a href=#event-appcache-obsolete>obsolete</a></code>!) at the
<code><a href=#applicationcache>ApplicationCache</a></code> singleton of the <a href=#cache-host>cache
host</a> the <code>Document</code> for this entry, if there
still is one. The default action of this event must be, if the
@@ -50488,7 +50488,7 @@
<p>If the download failed (e.g. the connection times out, or the
user cancels the download), then <a href=#queue-a-task>queue a task</a> to
- <a href=#fire-a-simple-event>fire a simple event</a> that is cancelable called <code title=event-appcache-error><a href=#event-appcache-error>error</a></code> at the
+ <a href=#fire-a-simple-event>fire a simple event</a> that is cancelable named <code title=event-appcache-error><a href=#event-appcache-error>error</a></code> at the
<code><a href=#applicationcache>ApplicationCache</a></code> singleton of the <a href=#cache-host>cache
host</a> the <code>Document</code> for this entry, if there
still is one. The default action of this event must be, if the
@@ -50513,7 +50513,7 @@
<li><p>For each <a href=#cache-host>cache host</a> associated with an
<a href=#application-cache>application cache</a> in <var title="">cache
group</var>, <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple
- event</a> that is cancelable called <code title=event-appcache-noupdate><a href=#event-appcache-noupdate>noupdate</a></code> at the
+ event</a> that is cancelable named <code title=event-appcache-noupdate><a href=#event-appcache-noupdate>noupdate</a></code> at the
<code><a href=#applicationcache>ApplicationCache</a></code> singleton of the <a href=#cache-host>cache
host</a>. The default action of these events must be, if the
user agent <a href=#shows-caching-progress>shows caching progress</a>, the display of
@@ -50547,7 +50547,7 @@
<li><p>For each <a href=#cache-host>cache host</a> associated with an
<a href=#application-cache>application cache</a> in <var title="">cache group</var>,
<a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple event</a> that
- is cancelable called <code title=event-appcache-downloading><a href=#event-appcache-downloading>downloading</a></code> at the
+ is cancelable named <code title=event-appcache-downloading><a href=#event-appcache-downloading>downloading</a></code> at the
<code><a href=#applicationcache>ApplicationCache</a></code> singleton of the <a href=#cache-host>cache
host</a>. The default action of these events must be, if the
user agent <a href=#shows-caching-progress>shows caching progress</a>, the display of some
@@ -50759,7 +50759,7 @@
<var title="">new cache</var>.</li>
<li><p><a href=#queue-a-task>Queue a task</a> to <a href=#fire-a-simple-event>fire a simple
- event</a> that is cancelable called <code title=event-appcache-error><a href=#event-appcache-error>error</a></code> at the
+ event</a> that is cancelable named <code title=event-appcache-error><a href=#event-appcache-error>error</a></code> at the
<code><a href=#applicationcache>ApplicationCache</a></code> singleton of the
<code>Document</code> for this entry, if there still is one. The
default action of this event must be, if the user agent
@@ -50829,7 +50829,7 @@
attempt</a>, then for each <a href=#cache-host>cache host</a> associated
with an <a href=#application-cache>application cache</a> in <var title="">cache
group</var>, <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple
- event</a> that is cancelable called <code title=event-appcache-cached><a href=#event-appcache-cached>cached</a></code> at the
+ event</a> that is cancelable named <code title=event-appcache-cached><a href=#event-appcache-cached>cached</a></code> at the
<code><a href=#applicationcache>ApplicationCache</a></code> singleton of the <a href=#cache-host>cache
host</a>. The default action of these events must be, if the
user agent <a href=#shows-caching-progress>shows caching progress</a>, the display of
@@ -50841,7 +50841,7 @@
<a href=#cache-host>cache host</a> associated with an <a href=#application-cache>application
cache</a> in <var title="">cache group</var>, <a href=#queue-a-task>queue a
task</a> to <a href=#fire-a-simple-event>fire a simple event</a> that is cancelable
- called <code title=event-appcache-updateready><a href=#event-appcache-updateready>updateready</a></code>
+ named <code title=event-appcache-updateready><a href=#event-appcache-updateready>updateready</a></code>
at the <code><a href=#applicationcache>ApplicationCache</a></code> singleton of the <a href=#cache-host>cache
host</a>. The default action of these events must be, if the
user agent <a href=#shows-caching-progress>shows caching progress</a>, the display of
@@ -50873,7 +50873,7 @@
its <a href=#application-cache>application cache</a>, if it has one.</li>
<li><p><a href=#queue-a-task>Queue a task</a> to <a href=#fire-a-simple-event>fire a simple
- event</a> that is cancelable called <code title=event-appcache-error><a href=#event-appcache-error>error</a></code> at the
+ event</a> that is cancelable named <code title=event-appcache-error><a href=#event-appcache-error>error</a></code> at the
<code><a href=#applicationcache>ApplicationCache</a></code> singleton of the
<code>Document</code> for this entry, if there still is one. The
default action of these events must be, if the user agent
@@ -50886,7 +50886,7 @@
<li><p>For each <a href=#cache-host>cache host</a> still associated with an
<a href=#application-cache>application cache</a> in <var title="">cache group</var>,
<a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple event</a> that
- is cancelable called <code title=event-appcache-error><a href=#event-appcache-error>error</a></code> at the
+ is cancelable named <code title=event-appcache-error><a href=#event-appcache-error>error</a></code> at the
<code><a href=#applicationcache>ApplicationCache</a></code> singleton of the <a href=#cache-host>cache
host</a>. The default action of these events must be, if the
user agent <a href=#shows-caching-progress>shows caching progress</a>, the display of some
@@ -51360,13 +51360,13 @@
<p>When the value that would be returned by the <code title=dom-navigator-onLine><a href=#dom-navigator-online>navigator.onLine</a></code> attribute of
the <code><a href=#window>Window</a></code> changes from true to false, the user agent
- must <a href=#fire-a-simple-event>fire a simple event</a> called <dfn id=event-offline title=event-offline><code>offline</code></dfn> at the
+ must <a href=#fire-a-simple-event>fire a simple event</a> named <dfn id=event-offline title=event-offline><code>offline</code></dfn> at the
<code><a href=#window>Window</a></code> object.</p>
<p>On the other hand, when the value that would be returned by the
<code title=dom-navigator-onLine><a href=#dom-navigator-online>navigator.onLine</a></code> attribute
of the <code><a href=#window>Window</a></code> changes from false to true, the user
- agent must <a href=#fire-a-simple-event>fire a simple event</a> called <dfn id=event-online title=event-online><code>online</code></dfn> at the
+ agent must <a href=#fire-a-simple-event>fire a simple event</a> named <dfn id=event-online title=event-online><code>online</code></dfn> at the
<code><a href=#window>Window</a></code> object.</p>
</div>
@@ -53009,7 +53009,7 @@
</li>
- <li><p><a href=#fire-a-simple-event>Fire a simple event</a> called <code title=event-unload>unload</code> at the <code>Document</code>'s
+ <li><p><a href=#fire-a-simple-event>Fire a simple event</a> named <code title=event-unload>unload</code> at the <code>Document</code>'s
<code><a href=#window>Window</a></code> object.</li>
<li><p>If any event listeners were triggered by the previous step,
@@ -53065,7 +53065,7 @@
<p>If the user cancels any instance of the <a href=#fetch title=fetch>fetching algorithm</a> in the context of a
<code>Document</code> in a <a href=#browsing-context>browsing context</a>, then, if
that <code>Document</code> is an <a href=#active-document>active document</a>, the
- user agent must <a href=#fire-a-simple-event>fire a simple event</a> called <code title=event-abort>abort</code> at that <code>Document</code>'s
+ user agent must <a href=#fire-a-simple-event>fire a simple event</a> named <code title=event-abort>abort</code> at that <code>Document</code>'s
<code><a href=#window>Window</a></code> object.</p>
<!-- I'd love to make this more precise, anyone have any suggestions
@@ -54780,7 +54780,7 @@
</li>
- <li><p><a href=#fire-a-simple-event>Fire a simple event</a> called <code title=event-focus>focus</code> at the element.</li>
+ <li><p><a href=#fire-a-simple-event>Fire a simple event</a> named <code title=event-focus>focus</code> at the element.</li>
</ol><p>User agents must run the <a href=#focusing-steps>focusing steps</a> for an
element whenever the user moves the focus to a
@@ -54793,13 +54793,13 @@
element, and the element does not have a defined <a href=#activation-behavior>activation
behavior</a>, and the user has changed the element's <a href=#concept-fe-value title=concept-fe-value>value</a> or its list of <a href=#concept-input-type-file-selected title=concept-input-type-file-selected>selected files</a>
while the control was focused without committing that change, then
- <a href=#fire-a-simple-event>fire a simple event</a> that bubbles called <code title=event-change>change</code> at the element, then
+ <a href=#fire-a-simple-event>fire a simple event</a> that bubbles named <code title=event-change>change</code> at the element, then
<a href=#broadcast-formchange-events>broadcast <code title=event-formchange>formchange</code>
events</a> at the element's <a href=#form-owner>form owner</a>.</p>
<li><p>Unfocus the element.</li>
- <li><p><a href=#fire-a-simple-event>Fire a simple event</a> called <code title=event-blur>blur</code> at the element.</li>
+ <li><p><a href=#fire-a-simple-event>Fire a simple event</a> named <code title=event-blur>blur</code> at the element.</li>
</ol><p>When an element that is focused stops being a
<a href=#focusable>focusable</a> element, or stops being focused without
@@ -66115,7 +66115,7 @@
the parser stopped</a> have <a href=#completed-loading>completed loading</a> and
been <a href=#executing-a-script-block title="executing a script block">executed</a>, the
user agent must <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple
- event</a> called <code title=event-DOMContentLoaded>DOMContentLoaded</code> at the
+ event</a> named <code title=event-DOMContentLoaded>DOMContentLoaded</code> at the
<code>Document</code>. (If the list is empty, this happens
immediately.)</p>
@@ -66128,7 +66128,7 @@
<li>If the <code>Document</code> is in a <a href=#browsing-context>browsing
context</a>, then <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a
- simple event</a> called <code title=event-load>load</code> at
+ simple event</a> named <code title=event-load>load</code> at
the <code>Document</code>'s <code><a href=#window>Window</a></code> object, but with
its <code title=dom-event-target>target</code> set to the
<code>Document</code> object (and the <code title=dom-event-currentTarget>currentTarget</code> set to the
@@ -72034,7 +72034,7 @@
<p>When a <code><a href=#the-marquee-element>marquee</a></code> element is created, the user agent
must <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple event</a>
- called <code title=event-start>start</code> at the element.</p>
+ named <code title=event-start>start</code> at the element.</p>
<hr><p>The <dfn id=attr-marquee-behavior title=attr-marquee-behavior><code>behavior</code></dfn> content
attribute on <code><a href=#the-marquee-element>marquee</a></code> elements is an <a href=#enumerated-attribute>enumerated
@@ -72133,17 +72133,17 @@
or greater than the element's <a href=#marquee-loop-count>marquee loop count</a>,
<a href=#concept-marquee-off title=concept-marquee-off>turn off</a> the
<code><a href=#the-marquee-element>marquee</a></code> element and <a href=#queue-a-task>queue a task</a> to
- <a href=#fire-a-simple-event>fire a simple event</a> called <code title=event-finish>finish</code> at the <code><a href=#the-marquee-element>marquee</a></code>
+ <a href=#fire-a-simple-event>fire a simple event</a> named <code title=event-finish>finish</code> at the <code><a href=#the-marquee-element>marquee</a></code>
element.</p>
<p>Otherwise, if the <code title=attr-marquee-behavior><a href=#attr-marquee-behavior>behavior</a></code> attribute is in the
<a href=#attr-marquee-behavior-alternate title=attr-marquee-behavior-alternate>alternate</a>
state, then <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple
- event</a> called <code title=event-bounce>bounce</code> at
+ event</a> named <code title=event-bounce>bounce</code> at
the <code><a href=#the-marquee-element>marquee</a></code> element.</p>
<p>Otherwise, <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-simple-event>fire a simple
- event</a> called <code title=event-start>start</code> at the
+ event</a> named <code title=event-start>start</code> at the
<code><a href=#the-marquee-element>marquee</a></code> element.</p>
</li>
@@ -72277,10 +72277,10 @@
name</a> must be set to the empty string.</p>
<p>When content loads in a <code><a href=#frame>frame</a></code>, after any <code title=event-load>load</code> events are fired within the content
- itself, the user agent must <a href=#fire-a-simple-event>fire a simple event</a> called
+ itself, the user agent must <a href=#fire-a-simple-event>fire a simple event</a> named
<code title=event-load>load</code> at the <code><a href=#frame>frame</a></code>
element. When content fails to load (e.g. due to a network error),
- then the user agent must <a href=#fire-a-simple-event>fire a simple event</a> called
+ then the user agent must <a href=#fire-a-simple-event>fire a simple event</a> named
<code title=event-error>error</code> at the element instead.</p>
<p>When there is an <a href=#active-parser>active parser</a> in the
@@ -74468,6 +74468,7 @@
Remy Sharp,
Rene Saarsoo,
Rene Stach,
+ Ric Hardacre,
Rich Doughty,
Richard Ishida,
Rigo Wenning,
Modified: source
===================================================================
--- source 2009-10-04 11:27:00 UTC (rev 4071)
+++ source 2009-10-04 11:41:59 UTC (rev 4072)
@@ -6973,7 +6973,7 @@
<span>XML parser</span>, or to the string "complete"
otherwise. Various algorithms during page loading affect this
value. When the value is set, the user agent must <span>fire a
- simple event</span> called <code
+ simple event</span> named <code
title="event-readystatechange">readystatechange</code> at the
<code>Document</code> object.</p>
@@ -8986,7 +8986,7 @@
<p>When a user agent is to <dfn>run post-click activation
steps</dfn> on an element, the user agent must <span>fire a simple
- event</span> called <code
+ event</span> named <code
title="event-DOMActivate">DOMActivate</code> that is cancelable at
that element. The default action of this event must be to <span>run
final activation steps</span> on that element. If the event is
@@ -11071,13 +11071,13 @@
title="queue a task">queued</span> by the <span>networking task
source</span> once the resource has been <span
title="fetch">fetched</span> must, if the loads were successful,
- <span>queue a task</span> to <span>fire a simple event</span> called
+ <span>queue a task</span> to <span>fire a simple event</span> named
<code title="event-load">load</code> at the <code>link</code>
element; otherwise, if the resource or one of its subresources
failed to completely load for any reason (e.g. DNS error, HTTP 404
response, a connection being prematurely closed, unsupported
Content-Type), it must instead <span>queue a task</span> to
- <span>fire a simple event</span> called <code
+ <span>fire a simple event</span> named <code
title="event-error">error</code> at the <code>link</code>
element. Non-network errors in processing the resource or its
subresources (e.g. CSS parse errors, PNG decoding errors) are not
@@ -12432,13 +12432,13 @@
<p>Once the element has been evaluated, if it had no subresources or
once all the subresources it uses have been <span
title="fetch">fetched</span>, the user agent must <span>queue a
- task</span> to <span>fire a simple event</span> called <code
+ task</span> to <span>fire a simple event</span> named <code
title="event-load">load</code> at the <code>style</code> element. If
the resource has a subresource that fails to completely load for any
reason (e.g. DNS error, HTTP 404 response, the connection being
prematurely closed, unsupported Content-Type), the user agent must
instead <span>queue a task</span> to <span>fire a simple
- event</span> called <code title="event-error">error</code> at the
+ event</span> named <code title="event-error">error</code> at the
<code>style</code> element. Non-network errors in the processing of
the element's contents or its subresources (e.g. CSS parse errors)
are not failures for the purposes of this paragraph. The
@@ -13150,7 +13150,7 @@
an HTTP 404 error)</dt>
<dd><p>Executing the script block must just consist of <span
- title="fire a simple event">firing a simple event</span> called
+ title="fire a simple event">firing a simple event</span> named
<code title="event-error">error</code> at the element.</p></dd>
<dt>If the load was successful</dt>
@@ -13271,7 +13271,7 @@
<li>
- <p><span>Fire a simple event</span> called <code
+ <p><span>Fire a simple event</span> named <code
title="event-load">load</code> at the <code>script</code>
element.</p>
@@ -19865,7 +19865,7 @@
title="img-available">available</i></dt>
<dd><span>Queue a task</span> to <span>fire a simple event</span>
- called <code title="event-load">load</code> at the <code>img</code>
+ named <code title="event-load">load</code> at the <code>img</code>
element (this happens after <code
title="dom-img-complete">complete</code> starts returning
true).</dd>
@@ -19875,7 +19875,7 @@
image)</dt>
<dd><span>Queue a task</span> to <span>fire a simple event</span>
- called <code title="event-error">error</code> on the
+ named <code title="event-error">error</code> on the
<code>img</code> element.</dd>
</dl>
@@ -21280,10 +21280,10 @@
<p>When content loads in an <code>iframe</code>, after any <code
title="event-load">load</code> events are fired within the content
- itself, the user agent must <span>fire a simple event</span> called
+ itself, the user agent must <span>fire a simple event</span> named
<code title="event-load">load</code> at the <code>iframe</code>
element. When content fails to load (e.g. due to a network error),
- then the user agent must <span>fire a simple event</span> called
+ then the user agent must <span>fire a simple event</span> named
<code title="event-error">error</code> at the element instead.</p>
<p>When there is an <span>active parser</span> in the
@@ -22208,7 +22208,7 @@
<li><p>If the load failed (e.g. the <span>URL</span> could not be
<span title="resolve a url">resolved</span>, there was an HTTP
404 error, there was a DNS error), <span>fire a simple
- event</span> called <code title="event-error">error</code> at the
+ event</span> named <code title="event-error">error</code> at the
element, then jump to the last step in the overall set of steps
(fallback).</p></li>
@@ -22415,7 +22415,7 @@
<li>
<p>Once the resource is completely loaded, <span>queue a
- task</span> to <span>fire a simple event</span> called <code
+ task</span> to <span>fire a simple event</span> named <code
title="event-load">load</code> at the element.</p>
<p>The <span>task source</span> for this task<!--tasks mentioned
@@ -23834,11 +23834,11 @@
<code>MediaError</code> object whose <code
title="dom-MediaError-code">code</code> attribute is set to <code
title="dom-MediaError-MEDIA_ERR_ABORTED">MEDIA_ERR_ABORTED</code>,
- <span>fire a progress event</span> called <code
+ <span>fire a progress event</span> named <code
title="event-media-abort">abort</code> at the <span>media element</span>,
in the context of the <span title="fetch">fetching process</span>
that is in progress for the element, and <span>fire a progress
- event</span> called <code title="event-media-loadend">loadend</code> at
+ event</span> named <code title="event-media-loadend">loadend</code> at
the <span>media element</span>, in the context of the same <span
title="fetch">fetching process</span>.</p></li>
@@ -23846,7 +23846,7 @@
to null and the <span>autoplaying flag</span> to true.</p></li>
<li><p>If <var title="">emptied</var> is true, <span>fire a simple
- event</span> called <code title="event-media-emptied">emptied</code> at
+ event</span> named <code title="event-media-emptied">emptied</code> at
the <span>media element</span>.</p></li>
<li><p>Invoke the <span>media element</span>'s <span
@@ -23919,7 +23919,7 @@
title="dom-media-NETWORK_LOADING">NETWORK_LOADING</code>.</p></li>
<li><p>⌛ <span>Queue a task</span> to <span>fire a progress
- event</span> called <code title="event-media-loadstart">loadstart</code>
+ event</span> named <code title="event-media-loadstart">loadstart</code>
at the <span>media element</span>, with no relevant <span
title="fetch">fetching process</span>.</p></li>
@@ -23969,7 +23969,7 @@
value.</p></li>
<li><p><span>Queue a task</span> to <span>fire a progress
- event</span> called <code title="event-media-error">error</code> at the
+ event</span> named <code title="event-media-error">error</code> at the
<span>media element</span>, in the context of the <span
title="fetch">fetching process</span> that was used to try to
obtain the <span>media resource</span> in the <span
@@ -23977,7 +23977,7 @@
algorithm</span>.</p></li>
<li><p><span>Queue a task</span> to <span>fire a progress
- event</span> called <code title="event-media-loadend">loadend</code> at
+ event</span> named <code title="event-media-loadend">loadend</code> at
the <span>media element</span>, in the context of the <span
title="fetch">fetching process</span> that was used to try to
obtain the <span>media resource</span> in the <span
@@ -24099,7 +24099,7 @@
the load failed.</p></li>
<li><p><i title="">Failed</i>: <span>Queue a task</span> to
- <span>fire a simple event</span> called <code
+ <span>fire a simple event</span> named <code
title="event-error">error</code> at the <var
title="">candidate</var> element, in the context of the <span
title="fetch">fetching process</span> that was used to try to
@@ -24198,14 +24198,14 @@
<p>Every 350ms (±200ms) or for every byte received, whichever
is <em>least</em> frequent, <span>queue a task</span> to
- <span>fire a progress event</span> called <code
+ <span>fire a progress event</span> named <code
title="event-media-progress">progress</code> at the element, in the
context of the <span title="fetch">fetching process</span> started
by this instance of this algorithm.</p>
<p>If at any point the user agent has received no data for more
than about three seconds, then <span>queue a task</span> to
- <span>fire a progress event</span> called <code
+ <span>fire a progress event</span> named <code
title="event-media-stalled">stalled</code> at the element, in the
context of the <span title="fetch">fetching process</span> started
by this instance of this algorithm.</p>
@@ -24226,7 +24226,7 @@
suspended, the user agent must set the <code
title="dom-media-networkState">networkState</code> to <code
title="dom-media-NETWORK_IDLE">NETWORK_IDLE</code> and <span>queue
- a task</span> to <span>fire a progress event</span> called <code
+ a task</span> to <span>fire a progress event</span> named <code
title="event-media-suspend">suspend</code> at the element, in the
context of the <span title="fetch">fetching process</span> started
by this instance of this algorithm. If and when downloading of the
@@ -24341,7 +24341,7 @@
<p class="note">The user agent <a
href="#durationChange">will</a> <span>queue a task</span> to
- <span>fire a simple event</span> called <code
+ <span>fire a simple event</span> named <code
title="event-media-durationchange">durationchange</code> at the
element at this point.</p>
@@ -24350,7 +24350,7 @@
<li id="fire-loadedmetadata">
<p><span>Queue a task</span> to <span>fire a simple
- event</span> called <code
+ event</span> named <code
title="event-media-loadedmetadata">loadedmetadata</code> at the
element.</p>
@@ -24416,7 +24416,7 @@
<dd>
<p><span>Queue a task</span> to <span>fire a progress
- event</span> called <code title="event-media-progress">progress</code>
+ event</span> named <code title="event-media-progress">progress</code>
at the <span>media element</span>, in the context of the <span
title="fetch">fetching process</span> started by this instance
of this algorithm.</p>
@@ -24446,13 +24446,13 @@
title="dom-MediaError-MEDIA_ERR_NETWORK">MEDIA_ERR_NETWORK</code>.</p></li>
<li><p><span>Queue a task</span> to <span>fire a progress
- event</span> called <code title="event-media-error">error</code> at
+ event</span> named <code title="event-media-error">error</code> at
the <span>media element</span>, in the context of the <span
title="fetch">fetching process</span> started by this instance
of this algorithm.</p></li>
<li><p><span>Queue a task</span> to <span>fire a progress
- event</span> called <code title="event-media-loadend">loadend</code>
+ event</span> named <code title="event-media-loadend">loadend</code>
at the <span>media element</span>, in the context of the <span
title="fetch">fetching process</span> started by this instance
of this algorithm.</p></li>
@@ -24461,7 +24461,7 @@
title="dom-media-networkState">networkState</code> attribute to
the <span title="dom-media-NETWORK_EMPTY">NETWORK_EMPTY</span>
value and <span>queue a task</span> to <span>fire a simple
- event</span> called <code title="event-media-emptied">emptied</code>
+ event</span> named <code title="event-media-emptied">emptied</code>
at the element.</p></li>
<li><p>Set the element's <span>delaying-the-load-event
@@ -24499,13 +24499,13 @@
title="dom-MediaError-MEDIA_ERR_DECODE">MEDIA_ERR_DECODE</code>.</p></li>
<li><p><span>Queue a task</span> to <span>fire a progress
- event</span> called <code title="event-media-error">error</code> at
+ event</span> named <code title="event-media-error">error</code> at
the <span>media element</span>, in the context of the <span
title="fetch">fetching process</span> started by this instance
of this algorithm.</p></li>
<li><p><span>Queue a task</span> to <span>fire a progress
- event</span> called <code title="event-media-loadend">loadend</code>
+ event</span> named <code title="event-media-loadend">loadend</code>
at the <span>media element</span>, in the context of the <span
title="fetch">fetching process</span> started by this instance
of this algorithm.</p></li>
@@ -24514,7 +24514,7 @@
title="dom-media-networkState">networkState</code> attribute to
the <span title="dom-media-NETWORK_EMPTY">NETWORK_EMPTY</span>
value and <span>queue a task</span> to <span>fire a simple
- event</span> called <code title="event-media-emptied">emptied</code>
+ event</span> named <code title="event-media-emptied">emptied</code>
at the element.</p></li>
<li><p>Set the element's <span>delaying-the-load-event
@@ -24554,13 +24554,13 @@
title="dom-MediaError-MEDIA_ERR_ABORT">MEDIA_ERR_ABORT</code>.</p></li>
<li><p><span>Queue a task</span> to <span>fire a progress
- event</span> called <code title="event-media-abort">abort</code> at
+ event</span> named <code title="event-media-abort">abort</code> at
the <span>media element</span>, in the context of the <span
title="fetch">fetching process</span> started by this instance
of this algorithm.</p></li>
<li><p><span>Queue a task</span> to <span>fire a progress
- event</span> called <code title="event-media-loadend">loadend</code>
+ event</span> named <code title="event-media-loadend">loadend</code>
at the <span>media element</span>, in the context of the <span
title="fetch">fetching process</span> started by this instance
of this algorithm.</p></li>
@@ -24573,7 +24573,7 @@
title="dom-media-networkState">networkState</code> attribute to
the <span title="dom-media-NETWORK_EMPTY">NETWORK_EMPTY</span>
value and <span>queue a task</span> to <span>fire a simple
- event</span> called <code title="event-media-emptied">emptied</code>
+ event</span> named <code title="event-media-emptied">emptied</code>
at the element. Otherwise, set the element's <code
title="dom-media-networkState">networkState</code> attribute to
the <span title="dom-media-NETWORK_IDLE">NETWORK_IDLE</span>
@@ -24644,13 +24644,13 @@
title="dom-media-NETWORK_LOADED">NETWORK_LOADED</code>.</p></li>
<li><p><span>Queue a task</span> to <span>fire a progress
- event</span> called <code title="event-media-load">load</code> at the
+ event</span> named <code title="event-media-load">load</code> at the
<span>media element</span>, in the context of the <span
title="fetch">fetching process</span> started by this instance of
this algorithm.</p></li>
<li><p><span>Queue a task</span> to <span>fire a progress
- event</span> called <code title="event-media-loadend">loadend</code> at
+ event</span> named <code title="event-media-loadend">loadend</code> at
the <span>media element</span>, in the context of the <span
title="fetch">fetching process</span> started by this instance of
this algorithm.</p></li>
@@ -24815,7 +24815,7 @@
<p id="durationChange">When the length of the <span>media
resource</span> changes (e.g. from being unknown to known, or from a
previously established length to a new length) the user agent must
- <span>queue a task</span> to <span>fire a simple event</span> called
+ <span>queue a task</span> to <span>fire a simple event</span> named
<code title="event-media-durationchange">durationchange</code> at the
<span>media element</span>.</p>
@@ -24860,7 +24860,7 @@
position</span>; otherwise, if the user agent has not fired a <code
title="event-media-timeupdate">timeupdate</code> event at the element in
the past 15 to 250ms, then the user agent must <span>queue a
- task</span> to <span>fire a simple event</span> called <code
+ task</span> to <span>fire a simple event</span> named <code
title="event-media-timeupdate">timeupdate</code> at the element.</p>
<p class="note">Because of the above requirement and the requirement
@@ -25027,7 +25027,7 @@
this <span>media element</span> since the <code
title="dom-media-load">load()</code> algorithm was last invoked,
the user agent must <span>queue a task</span> to <span>fire a
- simple event</span> called <code
+ simple event</span> named <code
title="event-media-loadeddata">loadeddata</code> at the element.</p>
<p>If the new ready state is <code
@@ -25061,12 +25061,12 @@
<dd>
<p>The user agent must <span>queue a task</span> to <span>fire a
- simple event</span> called <code
+ simple event</span> named <code
title="event-media-canplay">canplay</code>.</p>
<p>If the element is <span>potentially playing</span>, the user
agent must <span>queue a task</span> to <span>fire a simple
- event</span> called <code
+ event</span> named <code
title="event-media-playing">playing</code>.</p>
</dd>
@@ -25080,10 +25080,10 @@
<p>If the previous ready state was <code
title="dom-media-HAVE_CURRENT_DATA">HAVE_CURRENT_DATA</code> or
less, the user agent must <span>queue a task</span> to <span>fire
- a simple event</span> called <code
+ a simple event</span> named <code
title="event-media-canplay">canplay</code>, and, if the element is also
<span>potentially playing</span>, <span>queue a task</span> to
- <span>fire a simple event</span> called <code
+ <span>fire a simple event</span> named <code
title="event-media-playing">playing</code>.</p>
<p>If the <span>autoplaying flag</span> is true, and the <code
@@ -25093,8 +25093,8 @@
then the user agent may also set the <code
title="dom-media-paused">paused</code> attribute to false,
<span>queue a task</span> to <span>fire a simple event</span>
- called <code title="event-media-play">play</code>, and <span>queue a
- task</span> to <span>fire a simple event</span> called <code
+ named <code title="event-media-play">play</code>, and <span>queue a
+ task</span> to <span>fire a simple event</span> named <code
title="event-media-playing">playing</code>.</p>
<p class="note">User agents are not required to autoplay, and it
@@ -25105,7 +25105,7 @@
to override the behavior if so desired.</p>
<p>In any case, the user agent must finally <span>queue a
- task</span> to <span>fire a simple event</span> called <code
+ task</span> to <span>fire a simple event</span> named <code
title="event-media-canplaythrough">canplaythrough</code>.</p>
</dd>
@@ -25394,7 +25394,7 @@
<p>When a <span>media element</span> that is <span>potentially
playing</span> stops playing because it has <span>paused for user
interaction</span>, the user agent must <span>queue a task</span> to
- <span>fire a simple event</span> called <code
+ <span>fire a simple event</span> named <code
title="event-media-timeupdate">timeupdate</code> at the element.</p>
<p id="fire-waiting-when-waiting">When a <span>media element</span>
@@ -25407,9 +25407,9 @@
for user interaction</span>, or the <span
title="dom-media-seek">seeking algorithm</span> being invoked, the
user agent must <span>queue a task</span> to <span>fire a simple
- event</span> called <code title="event-media-timeupdate">timeupdate</code>
+ event</span> named <code title="event-media-timeupdate">timeupdate</code>
at the element, and <span>queue a task</span> to <span>fire a simple
- event</span> called <code title="event-media-waiting">waiting</code> at
+ event</span> named <code title="event-media-waiting">waiting</code> at
the element.</p>
<p>When the <span>current playback position</span> reaches the end
@@ -25435,11 +25435,11 @@
true.</p></li>
<li><p>The user agent must <span>queue a task</span> to <span>fire
- a simple event</span> called <code
+ a simple event</span> named <code
title="event-media-timeupdate">timeupdate</code> at the element.</p></li>
<li><p>The user agent must <span>queue a task</span> to <span>fire
- a simple event</span> called <code title="event-media-ended">ended</code>
+ a simple event</span> named <code title="event-media-ended">ended</code>
at the element.</p></li>
</ol>
@@ -25454,7 +25454,7 @@
<li><p>Stop playback.</p></li>
<li><p>The user agent must <span>queue a task</span> to <span>fire
- a simple event</span> called <code
+ a simple event</span> named <code
title="event-media-timeupdate">timeupdate</code> at the element.</p></li>
</ol>
@@ -25500,7 +25500,7 @@
change value (either by being set by script or by being changed
directly by the user agent, e.g. in response to user control) the
user agent must <span>queue a task</span> to <span>fire a simple
- event</span> called <code title="event-media-ratechange">ratechange</code>
+ event</span> named <code title="event-media-ratechange">ratechange</code>
at the <span>media element</span>.</p>
<p>The <dfn title="dom-media-played"><code>played</code></dfn>
@@ -25533,7 +25533,7 @@
<p class="note">This <a href="#seekUpdate">will cause</a> the user
agent to <span>queue a task</span> to <span>fire a simple
- event</span> called <code
+ event</span> named <code
title="event-media-timeupdate">timeupdate</code> at the <span>media
element</span>.</p> <!-- if we're already playing at this point,
it might also fire 'waiting' -->
@@ -25552,7 +25552,7 @@
title="dom-media-paused">paused</code> to false.</p></li>
<li><p><span>Queue a task</span> to <span>fire a simple event</span>
- called <code title="event-media-play">play</code> at the element.</p></li>
+ named <code title="event-media-play">play</code> at the element.</p></li>
<li><p>If the <span>media element</span>'s <code
title="dom-media-readyState">readyState</code> attribute has the
@@ -25561,7 +25561,7 @@
<code
title="dom-media-HAVE_CURRENT_DATA">HAVE_CURRENT_DATA</code>,
<span>queue a task</span> to <span>fire a simple event</span>
- called <code title="event-media-waiting">waiting</code> at the
+ named <code title="event-media-waiting">waiting</code> at the
element.</p></li>
<li><p>Otherwise, the <span>media element</span>'s <code
@@ -25570,7 +25570,7 @@
title="dom-media-HAVE_FUTURE_DATA">HAVE_FUTURE_DATA</code> or
<code title="dom-media-HAVE_ENOUGH_DATA">HAVE_ENOUGH_DATA</code>;
<span>queue a task</span> to <span>fire a simple event</span>
- called <code title="event-media-playing">playing</code> at the
+ named <code title="event-media-playing">playing</code> at the
element.</p></li>
</ol>
@@ -25610,12 +25610,12 @@
title="dom-media-paused">paused</code> to true.</p></li>
<li><p><span>Queue a task</span> to <span>fire a simple
- event</span> called <code
+ event</span> named <code
title="event-media-timeupdate">timeupdate</code> at the
element.</p></li>
<li><p><span>Queue a task</span> to <span>fire a simple
- event</span> called <code title="event-media-pause">pause</code>
+ event</span> named <code title="event-media-pause">pause</code>
at the element.</p></li>
</ol>
@@ -25705,7 +25705,7 @@
user agent has not fired a <code
title="event-media-timeupdate">timeupdate</code> event at the element in
the past 15 to 250ms, then the user agent must <span>queue a
- task</span> to <span>fire a simple event</span> called <code
+ task</span> to <span>fire a simple event</span> named <code
title="event-media-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
@@ -25843,7 +25843,7 @@
attribute must be set to true.</p></li>
<li id="seekUpdate"><p>The user agent must <span>queue a
- task</span> to <span>fire a simple event</span> called <code
+ task</span> to <span>fire a simple event</span> named <code
title="event-media-timeupdate">timeupdate</code> at the element.</p></li>
<li><p>If the <span>media element</span> was <span>potentially
@@ -25852,7 +25852,7 @@
attribute to change to a value lower than <code
title="dom-media-HAVE_FUTURE_DATA">HAVE_FUTURE_DATA</code>, the
user agent must <span>queue a task</span> to <span>fire a simple
- event</span> called <code title="event-media-waiting">waiting</code> at
+ event</span> named <code title="event-media-waiting">waiting</code> at
the element.</p></li>
<li><p>If, when it reaches this step, the user agent has still not
@@ -25860,7 +25860,7 @@
title="">new playback position</var> is available, and, if it is,
decoded enough data to play back that position, the user agent must
<span>queue a task</span> to <span>fire a simple event</span>
- called <code title="event-media-seeking">seeking</code> at the
+ named <code title="event-media-seeking">seeking</code> at the
element.</p></li>
<li><p>If the seek was in response to a DOM method call or setting
@@ -25876,7 +25876,7 @@
attribute must be set to false.</p></li>
<li><p>The user agent must <span>queue a task</span> to <span>fire
- a simple event</span> called <code
+ a simple event</span> named <code
title="event-media-seeked">seeked</code> at the element.</p></li>
</ol>
@@ -26015,7 +26015,7 @@
<p>Whenever either the <code title="dom-media-muted">muted</code> or
<code title="dom-media-volume">volume</code> attributes are changed,
the user agent must <span>queue a task</span> to <span>fire a simple
- event</span> called <code
+ event</span> named <code
title="event-media-volumechange">volumechange</code> at the <span>media
element</span>.</p>
@@ -38185,7 +38185,7 @@
title="dom-input-indeterminate">indeterminate</code> IDL attribute
back to the values they had before the <span>pre-click activation
steps</span> were run. The <span>activation behavior</span> is to
- <span>fire a simple event</span> that bubbles called <code
+ <span>fire a simple event</span> that bubbles named <code
title="event-change">change</code> at the element<!-- It's not
cancelable. Once this fires, the control is checked, end of
story. -->, then <span>broadcast <code
@@ -38348,7 +38348,7 @@
true. The <span>canceled activation steps</span> consist of setting
the element's <span title="concept-fe-checked">checkedness</span> to
false. The <span>activation behavior</span> is to <span>fire a
- simple event</span> that bubbles called <code
+ simple event</span> that bubbles named <code
title="event-change">change</code> at the element<!-- It's not
cancelable. Once this fires, the control is checked, end of
story. -->, then <span>broadcast <code
@@ -38823,12 +38823,12 @@
source</span> once the resource has been <span
title="fetch">fetched</span>, must, if the download was successful
and the image is <i title="input-img-available">available</i>,
- <span>queue a task</span> to <span>fire a simple event</span> called
+ <span>queue a task</span> to <span>fire a simple event</span> named
<code title="event-load">load</code> at the <code>input</code>
element; and otherwise, if the fetching process fails without a
response from the remote server, or completes but the image is not a
valid or supported image, <span>queue a task</span> to <span>fire a
- simple event</span> called <code title="event-error">error</code> on
+ simple event</span> named <code title="event-error">error</code> on
the <code>input</code> element.</p>
<hr>
@@ -40218,7 +40218,7 @@
event applies, any time the user causes the element's <span
title="concept-fe-value">value</span> to change, the user agent must
<span>queue a task</span> to <span>fire a simple event</span> that
- bubbles called <code title="event-input">input</code> at the
+ bubbles named <code title="event-input">input</code> at the
<code>input</code> element, then <span>broadcast <code
title="event-forminput">forminput</code> events</span> at the
<code>input</code> element's <span>form owner</span>. User agents
@@ -40244,7 +40244,7 @@
<span title="concept-fe-value">value</span> or list of <span
title="concept-input-type-file-selected">selected files</span>, the
user agent must <span>queue a task</span> to <span>fire a simple
- event</span> that bubbles called <code
+ event</span> that bubbles named <code
title="event-change">change</code> at the <code>input</code>
element, then <span>broadcast <code
title="event-formchange">formchange</code> events</span> at the
@@ -40274,7 +40274,7 @@
<li>If the <code title="event-input-input">input</code> event
applies, <span>queue a task</span> to <span>fire a simple
- event</span> that bubbles called <code
+ event</span> that bubbles named <code
title="event-input">input</code> at the <code>input</code>
element.</li>
@@ -40285,7 +40285,7 @@
<li>If the <code title="event-input-change">change</code> event
applies, <span>queue a task</span> to <span>fire a simple
- event</span> that bubbles called <code
+ event</span> that bubbles named <code
title="event-change">change</code> at the <code>input</code>
element.</li>
@@ -40626,7 +40626,7 @@
set the <span
title="concept-option-selectedness">selectedness</span> of the
picked <code>option</code> element to true and then <span>queue a
- task</span> to <span>fire a simple event</span> that bubbles called
+ task</span> to <span>fire a simple event</span> that bubbles named
<code title="event-change">change</code> at the <code>select</code>
element, using the <span>user interaction task source</span> as the
task source, then <span>broadcast <code
@@ -40679,7 +40679,7 @@
spec point --> is queued (e.g. before a related <span
title="event-click">click</span> event), the user agent must
<span>queue a task</span> to <span>fire a simple event</span> that
- bubbles called <code title="event-change">change</code> at the
+ bubbles named <code title="event-change">change</code> at the
<code>select</code> element, using the <span>user interaction task
source</span> as the task source, then <span>broadcast <code
title="event-formchange">formchange</code> events</span> at the
@@ -41482,7 +41482,7 @@
editable by the user. Any time the user causes the element's <span
title="concept-textarea-raw-value">raw value</span> to change, the
user agent must <span>queue a task</span> to <span>fire a simple
- event</span> that bubbles called <code
+ event</span> that bubbles named <code
title="event-input">input</code> at the <code>textarea</code>
element, then <span>broadcast <code
title="event-forminput">forminput</code> events</span> at the
@@ -42984,7 +42984,7 @@
<ol>
- <li><p><span>Fire a simple event</span> called <code
+ <li><p><span>Fire a simple event</span> named <code
title="event-invalid">invalid</code> that is cancelable at <var
title="">field</var>.</p></li>
@@ -43261,7 +43261,7 @@
method is invoked, if the element is a <span>candidate for
constraint validation</span> and does not <span
title="concept-fv-valid">satisfy its constraints</span>, the user
- agent must <span>fire a simple event</span> called <code
+ agent must <span>fire a simple event</span> named <code
title="event-invalid">invalid</code> that is cancelable (but in this
case has no default action) at the element and return
false. Otherwise, it must only return true without doing anything
@@ -43421,7 +43421,7 @@
these steps.</p></li>
<li><p>If the <var title="">scripted-submit</var> flag is not set,
- then <span>fire a simple event</span> that is cancelable called
+ then <span>fire a simple event</span> that is cancelable named
<code title="event-submit">submit</code>, at <var
title="">form</var>. If the event's default action is prevented
(i.e. if the event is canceled) then abort these steps. Otherwise,
@@ -44292,7 +44292,7 @@
<p>When a form <var title="">form</var> is <dfn
title="concept-form-reset">reset</dfn>, the user agent must
- <span>fire a simple event</span> called <code
+ <span>fire a simple event</span> named <code
title="event-reset">reset</code>, that is cancelable, at <var
title="">form</var>, and then, if that event is not canceled, must
invoke the <span title="concept-form-reset-control">reset
@@ -44339,7 +44339,7 @@
title="event-formchange">formchange</code>.</li>
<li><p>For each element in <var title="">controls</var>, in
- <span>tree order</span>, <span>fire a simple event</span> called
+ <span>tree order</span>, <span>fire a simple event</span> named
<var title="">event name</var> at the element.</p></li>
</ol>
@@ -47534,7 +47534,7 @@
<p>When an element's context menu is requested (e.g. by the user
right-clicking the element, or pressing a context menu key), the UA
- must <span>fire a simple event</span> called <code
+ must <span>fire a simple event</span> named <code
title="event-contextmenu">contextmenu</code> that bubbles and is
cancelable at the element for which the menu was requested.</p>
@@ -47554,7 +47554,7 @@
<p>If the element or one of its ancestors <em>does</em> have a
context menu assigned, then the user agent must <span>fire a simple
- event</span> called <code title="event-show">show</code> at the
+ event</span> named <code title="event-show">show</code> at the
<code>menu</code> element of the context menu of the nearest
ancestor (including the element itself) with one assigned.</p>
<!-- v2: include modifier key information -->
@@ -57481,14 +57481,14 @@
values appropriately describing the state of the key input device at
the time the event is created.</p>
- <p><dfn title="fire a simple event">Firing a simple event called
+ <p><dfn title="fire a simple event">Firing a simple event named
<var title="">e</var></dfn> means that an event with the name <var
title="">e</var>, with no namespace, which does not bubble (except
where otherwise stated) and is not cancelable (except where
otherwise stated), and which uses the <code>Event</code> interface,
must be dispatched at the given target.</p>
- <p><dfn title="fire a progress event">Firing a progress event called
+ <p><dfn title="fire a progress event">Firing a progress event named
<var title="">e</var></dfn>, optionally in the context of a
particular instance of the <span title="fetch">fetching
algorithm</span>, means that an event with the name <var
@@ -58099,7 +58099,7 @@
<li>
- <p>The user agent must <span>fire a simple event</span> called
+ <p>The user agent must <span>fire a simple event</span> named
<code title="event-beforeprint">beforeprint</code> at the
<code>Window</code> object of the <code>Document</code> that is
being printed, as well as any <span title="nested browsing
@@ -58134,7 +58134,7 @@
<li>
- <p>The user agent must <span>fire a simple event</span> called
+ <p>The user agent must <span>fire a simple event</span> named
<code title="event-afterprint">afterprint</code> at the
<code>Window</code> object of the <code>Document</code> that is
being printed, as well as any <span title="nested browsing
@@ -59976,7 +59976,7 @@
title="concept-appcache-status">status</span> of <var
title="">cache group</var> is <i>checking</i> or
<i>downloading</i>, then <span>queue a task</span> to <span>fire
- a simple event</span> called <code
+ a simple event</span> named <code
title="event-appcache-checking">checking</code> at the
<code>ApplicationCache</code> singleton of that <span>cache
host</span>. The default action of this event must be, if the
@@ -59990,7 +59990,7 @@
title="concept-appcache-status">status</span> of <var
title="">cache group</var> is <i>downloading</i>, then also
<span>queue a task</span> to <span>fire a simple event</span>
- called <code
+ named <code
title="event-appcache-downloading">downloading</code> that is
cancelable at the <code>ApplicationCache</code> singleton of that
<span>cache host</span>. The default action of this event must
@@ -60010,7 +60010,7 @@
<li><p>For each <span>cache host</span> associated with an
<span>application cache</span> in <var title="">cache
group</var>, <span>queue a task</span> to <span>fire a simple
- event</span> that is cancelable called <code
+ event</span> that is cancelable named <code
title="event-appcache-checking">checking</code> at the
<code>ApplicationCache</code> singleton of the <span>cache
host</span>. The default action of these events must be, if the
@@ -60033,7 +60033,7 @@
<li><p>If this is a <span title="concept-appcache-cache">cache
attempt</span>, then this algorithm was invoked with a <span>cache
host</span>; <span>queue a task</span> to <span>fire a simple
- event</span> called <code
+ event</span> named <code
title="event-appcache-checking">checking</code> that is cancelable
at the <code>ApplicationCache</code> singleton of that <span>cache
host</span>. The default action of this event must be, if the user
@@ -60082,7 +60082,7 @@
<li><p>For each <span>cache host</span> associated with an
<span>application cache</span> in <var title="">cache
group</var>, <span>queue a task</span> to <span>fire a simple
- event</span> called <code
+ event</span> named <code
title="event-appcache-obsolete">obsolete</code> that is
cancelable at the <code>ApplicationCache</code> singleton of the
<span>cache host</span>. The default action of these events must
@@ -60094,7 +60094,7 @@
<li><p>For each entry in <var title="">cache group</var>'s <span
title="concept-appcache-pending-masters">list of pending master
entries</span>, <span>queue a task</span> to <span>fire a simple
- event</span> that is cancelable called <code
+ event</span> that is cancelable named <code
title="event-appcache-error">error</code> (not <code
title="event-appcache-obsolete">obsolete</code>!) at the
<code>ApplicationCache</code> singleton of the <span>cache
@@ -60163,7 +60163,7 @@
<p>If the download failed (e.g. the connection times out, or the
user cancels the download), then <span>queue a task</span> to
- <span>fire a simple event</span> that is cancelable called <code
+ <span>fire a simple event</span> that is cancelable named <code
title="event-appcache-error">error</code> at the
<code>ApplicationCache</code> singleton of the <span>cache
host</span> the <code>Document</code> for this entry, if there
@@ -60192,7 +60192,7 @@
<li><p>For each <span>cache host</span> associated with an
<span>application cache</span> in <var title="">cache
group</var>, <span>queue a task</span> to <span>fire a simple
- event</span> that is cancelable called <code
+ event</span> that is cancelable named <code
title="event-appcache-noupdate">noupdate</code> at the
<code>ApplicationCache</code> singleton of the <span>cache
host</span>. The default action of these events must be, if the
@@ -60234,7 +60234,7 @@
<li><p>For each <span>cache host</span> associated with an
<span>application cache</span> in <var title="">cache group</var>,
<span>queue a task</span> to <span>fire a simple event</span> that
- is cancelable called <code
+ is cancelable named <code
title="event-appcache-downloading">downloading</code> at the
<code>ApplicationCache</code> singleton of the <span>cache
host</span>. The default action of these events must be, if the
@@ -60479,7 +60479,7 @@
<var title="">new cache</var>.</p></li>
<li><p><span>Queue a task</span> to <span>fire a simple
- event</span> that is cancelable called <code
+ event</span> that is cancelable named <code
title="event-appcache-error">error</code> at the
<code>ApplicationCache</code> singleton of the
<code>Document</code> for this entry, if there still is one. The
@@ -60563,7 +60563,7 @@
attempt</span>, then for each <span>cache host</span> associated
with an <span>application cache</span> in <var title="">cache
group</var>, <span>queue a task</span> to <span>fire a simple
- event</span> that is cancelable called <code
+ event</span> that is cancelable named <code
title="event-appcache-cached">cached</code> at the
<code>ApplicationCache</code> singleton of the <span>cache
host</span>. The default action of these events must be, if the
@@ -60577,7 +60577,7 @@
<span>cache host</span> associated with an <span>application
cache</span> in <var title="">cache group</var>, <span>queue a
task</span> to <span>fire a simple event</span> that is cancelable
- called <code title="event-appcache-updateready">updateready</code>
+ named <code title="event-appcache-updateready">updateready</code>
at the <code>ApplicationCache</code> singleton of the <span>cache
host</span>. The default action of these events must be, if the
user agent <span>shows caching progress</span>, the display of
@@ -60616,7 +60616,7 @@
its <span>application cache</span>, if it has one.</p></li>
<li><p><span>Queue a task</span> to <span>fire a simple
- event</span> that is cancelable called <code
+ event</span> that is cancelable named <code
title="event-appcache-error">error</code> at the
<code>ApplicationCache</code> singleton of the
<code>Document</code> for this entry, if there still is one. The
@@ -60632,7 +60632,7 @@
<li><p>For each <span>cache host</span> still associated with an
<span>application cache</span> in <var title="">cache group</var>,
<span>queue a task</span> to <span>fire a simple event</span> that
- is cancelable called <code
+ is cancelable named <code
title="event-appcache-error">error</code> at the
<code>ApplicationCache</code> singleton of the <span>cache
host</span>. The default action of these events must be, if the
@@ -61187,14 +61187,14 @@
<p>When the value that would be returned by the <code
title="dom-navigator-onLine">navigator.onLine</code> attribute of
the <code>Window</code> changes from true to false, the user agent
- must <span>fire a simple event</span> called <dfn
+ must <span>fire a simple event</span> named <dfn
title="event-offline"><code>offline</code></dfn> at the
<code>Window</code> object.</p>
<p>On the other hand, when the value that would be returned by the
<code title="dom-navigator-onLine">navigator.onLine</code> attribute
of the <code>Window</code> changes from false to true, the user
- agent must <span>fire a simple event</span> called <dfn
+ agent must <span>fire a simple event</span> named <dfn
title="event-online"><code>online</code></dfn> at the
<code>Window</code> object.</p>
@@ -63096,7 +63096,7 @@
</li>
- <li><p><span>Fire a simple event</span> called <code
+ <li><p><span>Fire a simple event</span> named <code
title="event-unload">unload</code> at the <code>Document</code>'s
<code>Window</code> object.</p></li>
@@ -63165,7 +63165,7 @@
title="fetch">fetching algorithm</span> in the context of a
<code>Document</code> in a <span>browsing context</span>, then, if
that <code>Document</code> is an <span>active document</span>, the
- user agent must <span>fire a simple event</span> called <code
+ user agent must <span>fire a simple event</span> named <code
title="event-abort">abort</code> at that <code>Document</code>'s
<code>Window</code> object.</p>
@@ -67004,7 +67004,7 @@
</li>
- <li><p><span>Fire a simple event</span> called <code
+ <li><p><span>Fire a simple event</span> named <code
title="event-focus">focus</code> at the element.</p></li>
</ol>
@@ -67024,14 +67024,14 @@
title="concept-fe-value">value</span> or its list of <span
title="concept-input-type-file-selected">selected files</span>
while the control was focused without committing that change, then
- <span>fire a simple event</span> that bubbles called <code
+ <span>fire a simple event</span> that bubbles named <code
title="event-change">change</code> at the element, then
<span>broadcast <code title="event-formchange">formchange</code>
events</span> at the element's <span>form owner</span>.</p>
<li><p>Unfocus the element.</p></li>
- <li><p><span>Fire a simple event</span> called <code
+ <li><p><span>Fire a simple event</span> named <code
title="event-blur">blur</code> at the element.</p></li>
</ol>
@@ -71330,7 +71330,7 @@
<!-- v2-onclose
<li><p><span>Queue a task</span> to <span>fire a simple
- event</span> called <code title="event-close">close</code> at the
+ event</span> named <code title="event-close">close</code> at the
<code>WorkerGlobalScope</code> object.</p></li>
-->
@@ -71705,7 +71705,7 @@
each <code>Worker</code> or <code>SharedWorker</code> object
associated with <var title="">worker global scope</var>,
<span>queue a task</span> to <span>fire a simple event</span>
- called <code title="event-error">error</code> at that
+ named <code title="event-error">error</code> at that
object. Abort these steps.</p>
<p>If the attempt succeeds, then <span title="decode a script
@@ -71761,7 +71761,7 @@
scope</var>'s <span
title="dom-WorkerGlobalScope-closing">closing</span> flag is set
to true<!-- v2-onclose and <span title="queue a task">a task is
- queued</span> to <span>fire a simple event</span> called <code
+ queued</span> to <span>fire a simple event</span> named <code
title="event-close">close</code> at <var title="">worker global
scope</var>-->.</p>
@@ -71874,7 +71874,7 @@
<p>For each <code>Worker</code> or <code>SharedWorker</code>
object associated with <var title="">worker global scope</var>,
<span>queue a task</span> to <span>fire a simple event</span>
- called <code title="event-close">close</code> at that object.</p>
+ named <code title="event-close">close</code> at that object.</p>
</li>
-->
@@ -71892,7 +71892,7 @@
<li><p>If the worker's <code>WorkerGlobalScope</code> object's
<span title="dom-WorkerGlobalScope-closing">closing</span> flag is
false, <span>queue a task</span> to <span>fire a simple
- event</span> called <code title="event-close">close</code> at the
+ event</span> named <code title="event-close">close</code> at the
worker's <code>WorkerGlobalScope</code> object.</p></li>
-->
@@ -73117,7 +73117,7 @@
user agent must set the <code
title="dom-EventSource-readyState">readyState</code> attribute to
<code title="dom-EventSource-OPEN">OPEN</code> and <span>queue a
- task</span> to <span>fire a simple event</span> called <code
+ task</span> to <span>fire a simple event</span> named <code
title="event-open">open</code> at the
<code>EventSource</code> object.</p>
@@ -73125,7 +73125,7 @@
agent must set the <code
title="dom-EventSource-readyState">readyState</code> attribute to
<code title="dom-EventSource-CONNECTING">CONNECTING</code>,
- <span>queue a task</span> to <span>fire a simple event</span> called
+ <span>queue a task</span> to <span>fire a simple event</span> named
<code title="event-error">error</code> at the
<code>EventSource</code> object, and then <span>fetch</span> the
event source resource again after a delay equal to the reconnection
@@ -73140,7 +73140,7 @@
agent must set the <code
title="dom-EventSource-readyState">readyState</code> attribute to
<code title="dom-EventSource-CLOSED">CLOSED</code> and <span>queue a
- task</span> to <span>fire a simple event</span> called <code
+ task</span> to <span>fire a simple event</span> named <code
title="event-error">error</code> at the <code>EventSource</code>
object. <strong>Once the user agent has <span title="fail the
connection">failed the connection</span>, it does <em>not</em>
@@ -73825,7 +73825,7 @@
<li>
<p><span>Queue a task</span> to <span>fire a simple event</span>
- called <code title="event-open">open</code> at the
+ named <code title="event-open">open</code> at the
<code>WebSocket</code> object.</p>
</li>
@@ -73850,7 +73850,7 @@
title="dom-WebSocket-readyState">readyState</code> attribute's value
must be changed to <code title="dom-WebSocket-CLOSED">CLOSED</code>
(2), and the user agent must <span>queue a task</span> to <span>fire
- a simple event</span> called <code
+ a simple event</span> named <code
title="event-close">close</code> at the
<code>WebSocket</code> object.</p>
@@ -84308,7 +84308,7 @@
the parser stopped</span> have <span>completed loading</span> and
been <span title="executing a script block">executed</span>, the
user agent must <span>queue a task</span> to <span>fire a simple
- event</span> called <code
+ event</span> named <code
title="event-DOMContentLoaded">DOMContentLoaded</code> at the
<code>Document</code>. (If the list is empty, this happens
immediately.)</p>
@@ -84328,7 +84328,7 @@
<li>If the <code>Document</code> is in a <span>browsing
context</span>, then <span>queue a task</span> to <span>fire a
- simple event</span> called <code title="event-load">load</code> at
+ simple event</span> named <code title="event-load">load</code> at
the <code>Document</code>'s <code>Window</code> object, but with
its <code title="dom-event-target">target</code> set to the
<code>Document</code> object (and the <code
@@ -88633,7 +88633,7 @@
<p>When a <code>marquee</code> element is created, the user agent
must <span>queue a task</span> to <span>fire a simple event</span>
- called <code title="event-start">start</code> at the element.</p>
+ named <code title="event-start">start</code> at the element.</p>
<hr>
@@ -88793,7 +88793,7 @@
or greater than the element's <span>marquee loop count</span>,
<span title="concept-marquee-off">turn off</span> the
<code>marquee</code> element and <span>queue a task</span> to
- <span>fire a simple event</span> called <code
+ <span>fire a simple event</span> named <code
title="event-finish">finish</code> at the <code>marquee</code>
element.</p>
@@ -88801,11 +88801,11 @@
title="attr-marquee-behavior">behavior</code> attribute is in the
<span title="attr-marquee-behavior-alternate">alternate</span>
state, then <span>queue a task</span> to <span>fire a simple
- event</span> called <code title="event-bounce">bounce</code> at
+ event</span> named <code title="event-bounce">bounce</code> at
the <code>marquee</code> element.</p>
<p>Otherwise, <span>queue a task</span> to <span>fire a simple
- event</span> called <code title="event-start">start</code> at the
+ event</span> named <code title="event-start">start</code> at the
<code>marquee</code> element.</p>
</li>
@@ -88975,10 +88975,10 @@
<p>When content loads in a <code>frame</code>, after any <code
title="event-load">load</code> events are fired within the content
- itself, the user agent must <span>fire a simple event</span> called
+ itself, the user agent must <span>fire a simple event</span> named
<code title="event-load">load</code> at the <code>frame</code>
element. When content fails to load (e.g. due to a network error),
- then the user agent must <span>fire a simple event</span> called
+ then the user agent must <span>fire a simple event</span> named
<code title="event-error">error</code> at the element instead.</p>
<p>When there is an <span>active parser</span> in the
@@ -91567,6 +91567,7 @@
Remy Sharp,
Rene Saarsoo,
Rene Stach,
+ Ric Hardacre,
Rich Doughty,
Richard Ishida,
Rigo Wenning,
More information about the Commit-Watchers
mailing list