[html5] r6188 - [e] (0) Update 'fire' and 'dispatch' terminology.
whatwg at whatwg.org
whatwg at whatwg.org
Fri Jun 3 17:46:46 PDT 2011
Author: ianh
Date: 2011-06-03 17:46:45 -0700 (Fri, 03 Jun 2011)
New Revision: 6188
Modified:
complete.html
index
source
Log:
[e] (0) Update 'fire' and 'dispatch' terminology.
Modified: complete.html
===================================================================
--- complete.html 2011-06-03 22:58:09 UTC (rev 6187)
+++ complete.html 2011-06-04 00:46:45 UTC (rev 6188)
@@ -239,7 +239,7 @@
<header class=head id=head><p><a class=logo href=http://www.whatwg.org/><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
<hgroup><h1>Web Applications 1.0</h1>
- <h2 class="no-num no-toc">Living Standard — Last Updated 3 June 2011</h2>
+ <h2 class="no-num no-toc">Living Standard — Last Updated 4 June 2011</h2>
</hgroup><dl><dt>Multiple-page version:</dt>
<dd><a href=http://www.whatwg.org/specs/web-apps/current-work/complete/>http://www.whatwg.org/specs/web-apps/current-work/complete/</a></dd>
<dt>One-page version:</dt>
@@ -2859,10 +2859,12 @@
operate on the actual underlying data, not a snapshot of the
data.</p>
- <p>The terms <dfn title="">fire</dfn> and <dfn title="">dispatch</dfn> are used interchangeably in the context of
- events, as in the DOM Events specifications. The term <dfn id=concept-events-trusted title=concept-events-trusted>trusted event</dfn> is used as
- defined by the DOM Events specification. <!--
- http://krijnhoetmer.nl/irc-logs/webapps/20091218 --> <a href=#refsDOMEVENTS>[DOMEVENTS]</a></p>
+ <p>In the contexts of events, the terms <dfn title="">fire</dfn> and
+ <dfn title="">dispatch</dfn> are used as defined in the DOM Core
+ specification: firing an event means to create and dispatch it, and
+ dispatching an event means to follow the steps that propagate the
+ event through the tree. The term <dfn id=concept-events-trusted title=concept-events-trusted>trusted event</dfn> is used to refer
+ to events that have the <span>trusted flag</span> set. <a href=#refsDOMCORE>[DOMCORE]</a></p>
<h4 id=plugins><span class=secno>2.1.5 </span>Plugins</h4>
@@ -7516,7 +7518,7 @@
returned. If, on the other hand, it fails or returns an out of range
value, or if the attribute is absent, the default value must be
returned instead, or −1 if there is no default value. On
- setting, if the value is negative, the user agent must fire an
+ setting, if the value is negative, the user agent must throw an
<code><a href=#index_size_err>INDEX_SIZE_ERR</a></code> exception. Otherwise, the given value
must be converted to the shortest possible string representing the
number as a <a href=#valid-non-negative-integer>valid non-negative integer</a> and then that
@@ -7550,7 +7552,7 @@
fails or returns an out of range value, or if the attribute is
absent, the default value must be returned instead, or 1 if there is
no default value. On setting, if the value is zero, the user agent
- must fire an <code><a href=#index_size_err>INDEX_SIZE_ERR</a></code> exception. Otherwise, the
+ must throw an <code><a href=#index_size_err>INDEX_SIZE_ERR</a></code> exception. Otherwise, the
given value must be converted to the shortest possible string
representing the number as a <a href=#valid-non-negative-integer>valid non-negative integer</a>
and then that string must be used as the new content attribute
@@ -16846,19 +16848,20 @@
handlers</a> with the same names normally supported by <a href=#html-elements>HTML
elements</a>.</p>
- <p class=example>Thus, for example, a bubbling <code title=event-error>error</code> event fired on a child of <a href=#the-body-element-0>the
- body element</a> of a <code><a href=#document>Document</a></code> would first trigger
- the <code title=handler-onerror><a href=#handler-onerror>onerror</a></code> <a href=#event-handler-content-attributes>event handler
- content attributes</a> of that element, then that of the root
- <code><a href=#the-html-element>html</a></code> element, and only <em>then</em> would it trigger
- the <code title=handler-window-onerror><a href=#handler-window-onerror>onerror</a></code> <a href=#event-handler-content-attributes title="event handler content attributes">event handler content
+ <p class=example>Thus, for example, a bubbling <code title=event-error>error</code> event dispatched on a child of
+ <a href=#the-body-element-0>the body element</a> of a <code><a href=#document>Document</a></code> would first
+ trigger the <code title=handler-onerror><a href=#handler-onerror>onerror</a></code> <a href=#event-handler-content-attributes>event
+ handler content attributes</a> of that element, then that of the
+ root <code><a href=#the-html-element>html</a></code> element, and only <em>then</em> would it
+ trigger the <code title=handler-window-onerror><a href=#handler-window-onerror>onerror</a></code>
+ <a href=#event-handler-content-attributes title="event handler content attributes">event handler content
attribute</a> on the <code><a href=#the-body-element>body</a></code> element. This is because
the event would bubble from the target, to the <code><a href=#the-body-element>body</a></code>, to
the <code><a href=#the-html-element>html</a></code>, to the <code><a href=#document>Document</a></code>, to the
<code><a href=#window>Window</a></code>, and the <a href=#event-handlers title="event handlers">event
handler</a> on the <code><a href=#the-body-element>body</a></code> is watching the
<code><a href=#window>Window</a></code> not the <code><a href=#the-body-element>body</a></code>. A regular event
- listener attached to the <code><a href=#the-body-element>body</a></code> using <code title="">addEventListener()</code>, however, would fire when the
+ listener attached to the <code><a href=#the-body-element>body</a></code> using <code title="">addEventListener()</code>, however, would be run when the
event bubbled through the <code><a href=#the-body-element>body</a></code> and not when it reaches
the <code><a href=#window>Window</a></code> object.</p>
@@ -27778,7 +27781,7 @@
even once the <a href=#ended-playback title="ended playback">playback has
ended</a>, because there is always the chance the user will
seek back to the start. In fact, in this situation, once <a href=#ended-playback title="ended playback">playback has ended</a>, the user agent
- will end up dispatching a <code title=event-media-stalled><a href=#event-media-stalled>stalled</a></code> event, as described
+ will end up firing a <code title=event-media-stalled><a href=#event-media-stalled>stalled</a></code> event, as described
earlier.</p>
</li>
@@ -33909,7 +33912,7 @@
<table><thead><tr><th>Event name
<th>Interface
- <th>Dispatched when...
+ <th>Fired when...
<th>Preconditions
<tbody><tr><td><dfn id=event-media-loadstart title=event-media-loadstart><code>loadstart</code></dfn>
@@ -34013,7 +34016,7 @@
<table><thead><tr><th>Event name
<th>Interface
- <th>Dispatched when...
+ <th>Fired when...
<tbody><tr><td><dfn id=event-mediacontroller-emptied title=event-MediaController-emptied><code>emptied</code></dfn>
<td><code><a href=#event>Event</a></code>
@@ -38309,12 +38312,13 @@
</li>
- </ol><p>Mouse clicks on an image associated with a set of layered shapes
- per the above algorithm must be dispatched to the top-most shape
- covering the point that the pointing device indicated (if any), and
- then, must be dispatched again (with a new <code><a href=#event>Event</a></code>
- object) to the image element itself. User agents may also allow
- individual <code><a href=#the-area-element>area</a></code> elements representing <a href=#hyperlink title=hyperlink>hyperlinks</a> to be selected and activated
+ </ol><p>Pointing device interaction with an image associated with a set
+ of layered shapes per the above algorithm must result in the
+ relevant user interaction events being first fired to the top-most
+ shape covering the point that the pointing device indicated (if
+ any), and then fired again (with a new <code><a href=#event>Event</a></code> object) to
+ the image element itself. User agents may also allow individual
+ <code><a href=#the-area-element>area</a></code> elements representing <a href=#hyperlink title=hyperlink>hyperlinks</a> to be selected and activated
(e.g. using a keyboard); events from this are not also propagated to
the image.</p>
@@ -52940,13 +52944,13 @@
<dl class=switch><dt>If the user requested a context menu using a pointing device</dt>
- <dd><p>The user agent must dispatch an event with the name <code title=event-contextmenu>contextmenu</code>, that bubbles and is
+ <dd><p>The user agent must fire an event with the name <code title=event-contextmenu>contextmenu</code>, that bubbles and is
cancelable, and that uses the <code><a href=#mouseevent>MouseEvent</a></code> interface, at
the element for which the menu was requested. The context
information of the event must be set to the same values as the last
- <code><a href=#mouseevent>MouseEvent</a></code> user interaction event that was dispatched
- as part of the gesture that that was interpreted as a request for
- the context menu.</dd>
+ <code><a href=#mouseevent>MouseEvent</a></code> user interaction event that was fired as
+ part of the gesture that that was interpreted as a request for the
+ context menu.</dd>
<dt>Otherwise</dt>
@@ -64782,7 +64786,7 @@
<table><thead><tr><th> Event name
<th> Interface
- <th> Dispatched when...
+ <th> Fired when...
<th> Next events
<tbody><tr><td> <dfn id=event-appcache-checking title=event-appcache-checking><code>checking</code></dfn>
<td> <code><a href=#event>Event</a></code>
@@ -67003,7 +67007,7 @@
<ol><li><p>If the <a href="#script's-global-object">script's global object</a> is a
<code><a href=#window>Window</a></code> object whose <code><a href=#document>Document</a></code> object is
not <a href=#fully-active>fully active</a>, then abort these steps without doing
- anything. The callback is not fired.</p>
+ anything. The callback is not run.</p>
<li><p>Set the <a href=#entry-script>entry script</a> to be the <a href=#concept-script title=concept-script>script</a> being invoked.</li>
@@ -67262,8 +67266,8 @@
given task to one of the <a href=#task-queue title="task queue">task queues</a>
of the relevant <a href=#event-loop>event loop</a>. All the tasks from one
particular <dfn id=task-source>task source</dfn> (e.g. the callbacks generated by
- timers, the events dispatched for mouse movements, the tasks queued
- for the parser) must always be added to the same <a href=#task-queue>task
+ timers, the events fired for mouse movements, the tasks queued for
+ the parser) must always be added to the same <a href=#task-queue>task
queue</a>, but tasks from different <a href=#task-source title="task
source">task sources</a> may be placed in different <a href=#task-queue title="task queue">task queues</a>.</p>
@@ -67423,7 +67427,7 @@
document">inserted into the document</a>.</p>
<!--
- <p>Asynchronous mutation events must be dispatched using <span
+ <p>Asynchronous mutation events must be fired using <span
title="concept-task">tasks</span> <span title="queue a
task">queued</span> with the <span>DOM manipulation task
source</span>. <a href="#refsDOMEVENTS">[DOMEVENTS]</a></p>
@@ -67438,7 +67442,7 @@
<p>This <a href=#task-source>task source</a> is used for features that react
to user interaction, for example keyboard or mouse input.</p>
- <p>Asynchronous events sent in response to user input (e.g. <code title=event-click><a href=#event-click>click</a></code> events) must be dispatched using
+ <p>Asynchronous events sent in response to user input (e.g. <code title=event-click><a href=#event-click>click</a></code> events) must be fired using
<a href=#concept-task title=concept-task>tasks</a> <a href=#queue-a-task title="queue a
task">queued</a> with the <a href=#user-interaction-task-source>user interaction task
source</a>. <a href=#refsDOMEVENTS>[DOMEVENTS]</a></p>
@@ -67827,7 +67831,7 @@
</div>
- <p class=note><a href=#event-handlers>Event handlers</a> <span class=impl>therefore</span> always fire before event listeners
+ <p class=note><a href=#event-handlers>Event handlers</a> <span class=impl>therefore</span> always run before event listeners
attached using <code title=dom-EventTarget-addEventListener>addEventListener()</code>.</p>
<div class=impl>
@@ -68034,16 +68038,16 @@
<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>, which does not bubble (except where otherwise
stated) and is not cancelable (except where otherwise stated), and
- which uses the <code><a href=#event>Event</a></code> interface, must be dispatched at
- the given target.</p>
+ which uses the <code><a href=#event>Event</a></code> interface, must be created and
+ dispatched at the given target.</p>
<p><dfn id=fire-a-synthetic-mouse-event title="fire a synthetic mouse event">Firing a synthetic
mouse event named <var title="">e</var></dfn> means that an event
with the name <var title="">e</var>, which does not bubble (except
where otherwise stated) and is not cancelable (except where
otherwise stated), and which uses the <code><a href=#mouseevent>MouseEvent</a></code>
- interface, must be dispatched at the given target. The event object
- must have its <code title="">screenX</code>, <code title="">screenY</code>, <code title="">clientX</code>, <code title="">clientY</code>, and <code title="">button</code> attributes
+ interface, must be created and dispatched at the given target. The
+ event object must have its <code title="">screenX</code>, <code title="">screenY</code>, <code title="">clientX</code>, <code title="">clientY</code>, and <code title="">button</code> attributes
set to 0, its <code title="">ctrlKey</code>, <code title="">shiftKey</code>, <code title="">altKey</code>, and <code title="">metaKey</code> attributes set according to the current
state of the key input device, if any (false for any keys that are
not available), its <code title="">detail</code> attribute set to 1,
@@ -68387,7 +68391,7 @@
</dd>
- </dl><p class=note>This API does not guarantee that timers will fire
+ </dl><p class=note>This API does not guarantee that timers will run
exactly on schedule. Delays due to CPU load, other tasks, etc, are
to be expected.</p>
@@ -71409,7 +71413,7 @@
</dd>
</dl><p><code><a href=#datatransfer>DataTransfer</a></code> objects are used during the <a href=#dndevents>drag-and-drop events</a>, and are only valid while
- those events are being dispatched.</p>
+ those events are being fired.</p>
<div class=impl>
@@ -75023,7 +75027,7 @@
<p>When a message sent in this manner from the other peer is
received, a <code title=event-stream-message><a href=#event-stream-message>message</a></code>
- event is dispatched at the <code><a href=#peerconnection>PeerConnection</a></code> object.</p>
+ event is fired at the <code><a href=#peerconnection>PeerConnection</a></code> object.</p>
<p>The maximum length of <var title="">text</var> is 504 bytes
after encoding the string as UTF-8; attempting to send a payload
@@ -75041,7 +75045,7 @@
<p>When the other peer starts sending a stream in this manner, an
<code title=event-stream-addstream><a href=#event-stream-addstream>addstream</a></code>
- event is dispatched at the <code><a href=#peerconnection>PeerConnection</a></code> object.</p>
+ event is fired at the <code><a href=#peerconnection>PeerConnection</a></code> object.</p>
</dd>
@@ -75053,7 +75057,7 @@
<p>When the other peer stops sending a stream in this manner, a
<code title=event-stream-removestream><a href=#event-stream-removestream>removestream</a></code>
- event is dispatched at the <code><a href=#peerconnection>PeerConnection</a></code> object.</p>
+ event is fired at the <code><a href=#peerconnection>PeerConnection</a></code> object.</p>
</dd>
@@ -75923,7 +75927,8 @@
<p><dfn id=fire-a-stream-event title="fire a stream event">Firing a stream event named <var title="">e</var></dfn> with a <code><a href=#stream>Stream</a></code> <var title="">stream</var> means that an event with the name <var title="">e</var>, which does not bubble (except where otherwise
stated) and is not cancelable (except where otherwise stated), and
- which uses the <code><a href=#streamevent>StreamEvent</a></code> interface with the <code title=dom-StreamEvent-stream><a href=#dom-streamevent-stream>stream</a></code> attribute set to <var title="">stream</var>, must be dispatched at the given target.</p>
+ which uses the <code><a href=#streamevent>StreamEvent</a></code> interface with the <code title=dom-StreamEvent-stream><a href=#dom-streamevent-stream>stream</a></code> attribute set to <var title="">stream</var>, must be created and dispatched at the given
+ target.</p>
</div>
@@ -75936,7 +75941,7 @@
<table><thead><tr><th>Event name
<th>Interface
- <th>Dispatched when...
+ <th>Fired when...
<tbody><tr><td><dfn id=event-stream-ended title=event-stream-ended><code>ended</code></dfn>
<td><code><a href=#event>Event</a></code>
@@ -75946,7 +75951,7 @@
<table><thead><tr><th>Event name
<th>Interface
- <th>Dispatched when...
+ <th>Fired when...
<tbody><tr><td><dfn id=event-stream-connecting title=event-stream-connecting><code>connecting</code></dfn>
<td><code><a href=#event>Event</a></code>
@@ -77534,16 +77539,16 @@
worker.</p>
<p>When the user agent is to <dfn id=fire-a-worker-error-event>fire a worker error event</dfn> at
- a <code><a href=#worker>Worker</a></code> object, it must dispatch an event that uses
- the <code><a href=#errorevent>ErrorEvent</a></code> interface, with the name <code title=event-error>error</code>, that doesn't bubble and is
+ a <code><a href=#worker>Worker</a></code> object, it must create and dispatch an event
+ that uses the <code><a href=#errorevent>ErrorEvent</a></code> interface, with the name <code title=event-error>error</code>, that doesn't bubble and is
cancelable, with its <code title=dom-ErrorEvent-message><a href=#dom-errorevent-message>message</a></code>, <code title=dom-ErrorEvent-filename><a href=#dom-errorevent-filename>filename</a></code>, and <code title=dom-ErrorEvent-lineno><a href=#dom-errorevent-lineno>lineno</a></code> attributes set
appropriately. The default action of this event depends on whether
the <code><a href=#worker>Worker</a></code> object is itself in a worker. If it is, and
that worker is also a dedicated worker, then the user agent must
again <a href=#queue-a-task>queue a task</a> to <a href=#fire-a-worker-error-event>fire a worker error
event</a> at the <code><a href=#worker>Worker</a></code> object associated with
- <em>that</em> worker. Otherwise, then the error may be reported
- to the user.</p>
+ <em>that</em> worker. Otherwise, then the error may be reported to
+ the user.</p>
<p>The <a href=#task-source>task source</a> for the tasks mentioned above is the
<a href=#dom-manipulation-task-source>DOM manipulation task source</a>.</p>
Modified: index
===================================================================
--- index 2011-06-03 22:58:09 UTC (rev 6187)
+++ index 2011-06-04 00:46:45 UTC (rev 6188)
@@ -243,7 +243,7 @@
<header class=head id=head><p><a class=logo href=http://www.whatwg.org/><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
<hgroup><h1 class=allcaps>HTML</h1>
- <h2 class="no-num no-toc">Living Standard — Last Updated 3 June 2011</h2>
+ <h2 class="no-num no-toc">Living Standard — Last Updated 4 June 2011</h2>
</hgroup><dl><dt><strong>Web developer edition</strong></dt>
<dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
<dt>Multiple-page version:</dt>
@@ -2876,10 +2876,12 @@
operate on the actual underlying data, not a snapshot of the
data.</p>
- <p>The terms <dfn title="">fire</dfn> and <dfn title="">dispatch</dfn> are used interchangeably in the context of
- events, as in the DOM Events specifications. The term <dfn id=concept-events-trusted title=concept-events-trusted>trusted event</dfn> is used as
- defined by the DOM Events specification. <!--
- http://krijnhoetmer.nl/irc-logs/webapps/20091218 --> <a href=#refsDOMEVENTS>[DOMEVENTS]</a></p>
+ <p>In the contexts of events, the terms <dfn title="">fire</dfn> and
+ <dfn title="">dispatch</dfn> are used as defined in the DOM Core
+ specification: firing an event means to create and dispatch it, and
+ dispatching an event means to follow the steps that propagate the
+ event through the tree. The term <dfn id=concept-events-trusted title=concept-events-trusted>trusted event</dfn> is used to refer
+ to events that have the <span>trusted flag</span> set. <a href=#refsDOMCORE>[DOMCORE]</a></p>
<h4 id=plugins><span class=secno>2.1.5 </span>Plugins</h4>
@@ -7502,7 +7504,7 @@
returned. If, on the other hand, it fails or returns an out of range
value, or if the attribute is absent, the default value must be
returned instead, or −1 if there is no default value. On
- setting, if the value is negative, the user agent must fire an
+ setting, if the value is negative, the user agent must throw an
<code><a href=#index_size_err>INDEX_SIZE_ERR</a></code> exception. Otherwise, the given value
must be converted to the shortest possible string representing the
number as a <a href=#valid-non-negative-integer>valid non-negative integer</a> and then that
@@ -7536,7 +7538,7 @@
fails or returns an out of range value, or if the attribute is
absent, the default value must be returned instead, or 1 if there is
no default value. On setting, if the value is zero, the user agent
- must fire an <code><a href=#index_size_err>INDEX_SIZE_ERR</a></code> exception. Otherwise, the
+ must throw an <code><a href=#index_size_err>INDEX_SIZE_ERR</a></code> exception. Otherwise, the
given value must be converted to the shortest possible string
representing the number as a <a href=#valid-non-negative-integer>valid non-negative integer</a>
and then that string must be used as the new content attribute
@@ -16832,19 +16834,20 @@
handlers</a> with the same names normally supported by <a href=#html-elements>HTML
elements</a>.</p>
- <p class=example>Thus, for example, a bubbling <code title=event-error>error</code> event fired on a child of <a href=#the-body-element-0>the
- body element</a> of a <code><a href=#document>Document</a></code> would first trigger
- the <code title=handler-onerror><a href=#handler-onerror>onerror</a></code> <a href=#event-handler-content-attributes>event handler
- content attributes</a> of that element, then that of the root
- <code><a href=#the-html-element>html</a></code> element, and only <em>then</em> would it trigger
- the <code title=handler-window-onerror><a href=#handler-window-onerror>onerror</a></code> <a href=#event-handler-content-attributes title="event handler content attributes">event handler content
+ <p class=example>Thus, for example, a bubbling <code title=event-error>error</code> event dispatched on a child of
+ <a href=#the-body-element-0>the body element</a> of a <code><a href=#document>Document</a></code> would first
+ trigger the <code title=handler-onerror><a href=#handler-onerror>onerror</a></code> <a href=#event-handler-content-attributes>event
+ handler content attributes</a> of that element, then that of the
+ root <code><a href=#the-html-element>html</a></code> element, and only <em>then</em> would it
+ trigger the <code title=handler-window-onerror><a href=#handler-window-onerror>onerror</a></code>
+ <a href=#event-handler-content-attributes title="event handler content attributes">event handler content
attribute</a> on the <code><a href=#the-body-element>body</a></code> element. This is because
the event would bubble from the target, to the <code><a href=#the-body-element>body</a></code>, to
the <code><a href=#the-html-element>html</a></code>, to the <code><a href=#document>Document</a></code>, to the
<code><a href=#window>Window</a></code>, and the <a href=#event-handlers title="event handlers">event
handler</a> on the <code><a href=#the-body-element>body</a></code> is watching the
<code><a href=#window>Window</a></code> not the <code><a href=#the-body-element>body</a></code>. A regular event
- listener attached to the <code><a href=#the-body-element>body</a></code> using <code title="">addEventListener()</code>, however, would fire when the
+ listener attached to the <code><a href=#the-body-element>body</a></code> using <code title="">addEventListener()</code>, however, would be run when the
event bubbled through the <code><a href=#the-body-element>body</a></code> and not when it reaches
the <code><a href=#window>Window</a></code> object.</p>
@@ -27767,7 +27770,7 @@
even once the <a href=#ended-playback title="ended playback">playback has
ended</a>, because there is always the chance the user will
seek back to the start. In fact, in this situation, once <a href=#ended-playback title="ended playback">playback has ended</a>, the user agent
- will end up dispatching a <code title=event-media-stalled><a href=#event-media-stalled>stalled</a></code> event, as described
+ will end up firing a <code title=event-media-stalled><a href=#event-media-stalled>stalled</a></code> event, as described
earlier.</p>
</li>
@@ -33898,7 +33901,7 @@
<table><thead><tr><th>Event name
<th>Interface
- <th>Dispatched when...
+ <th>Fired when...
<th>Preconditions
<tbody><tr><td><dfn id=event-media-loadstart title=event-media-loadstart><code>loadstart</code></dfn>
@@ -34002,7 +34005,7 @@
<table><thead><tr><th>Event name
<th>Interface
- <th>Dispatched when...
+ <th>Fired when...
<tbody><tr><td><dfn id=event-mediacontroller-emptied title=event-MediaController-emptied><code>emptied</code></dfn>
<td><code><a href=#event>Event</a></code>
@@ -38298,12 +38301,13 @@
</li>
- </ol><p>Mouse clicks on an image associated with a set of layered shapes
- per the above algorithm must be dispatched to the top-most shape
- covering the point that the pointing device indicated (if any), and
- then, must be dispatched again (with a new <code><a href=#event>Event</a></code>
- object) to the image element itself. User agents may also allow
- individual <code><a href=#the-area-element>area</a></code> elements representing <a href=#hyperlink title=hyperlink>hyperlinks</a> to be selected and activated
+ </ol><p>Pointing device interaction with an image associated with a set
+ of layered shapes per the above algorithm must result in the
+ relevant user interaction events being first fired to the top-most
+ shape covering the point that the pointing device indicated (if
+ any), and then fired again (with a new <code><a href=#event>Event</a></code> object) to
+ the image element itself. User agents may also allow individual
+ <code><a href=#the-area-element>area</a></code> elements representing <a href=#hyperlink title=hyperlink>hyperlinks</a> to be selected and activated
(e.g. using a keyboard); events from this are not also propagated to
the image.</p>
@@ -52929,13 +52933,13 @@
<dl class=switch><dt>If the user requested a context menu using a pointing device</dt>
- <dd><p>The user agent must dispatch an event with the name <code title=event-contextmenu>contextmenu</code>, that bubbles and is
+ <dd><p>The user agent must fire an event with the name <code title=event-contextmenu>contextmenu</code>, that bubbles and is
cancelable, and that uses the <code><a href=#mouseevent>MouseEvent</a></code> interface, at
the element for which the menu was requested. The context
information of the event must be set to the same values as the last
- <code><a href=#mouseevent>MouseEvent</a></code> user interaction event that was dispatched
- as part of the gesture that that was interpreted as a request for
- the context menu.</dd>
+ <code><a href=#mouseevent>MouseEvent</a></code> user interaction event that was fired as
+ part of the gesture that that was interpreted as a request for the
+ context menu.</dd>
<dt>Otherwise</dt>
@@ -64774,7 +64778,7 @@
<table><thead><tr><th> Event name
<th> Interface
- <th> Dispatched when...
+ <th> Fired when...
<th> Next events
<tbody><tr><td> <dfn id=event-appcache-checking title=event-appcache-checking><code>checking</code></dfn>
<td> <code><a href=#event>Event</a></code>
@@ -67007,7 +67011,7 @@
<ol><li><p>If the <a href="#script's-global-object">script's global object</a> is a
<code><a href=#window>Window</a></code> object whose <code><a href=#document>Document</a></code> object is
not <a href=#fully-active>fully active</a>, then abort these steps without doing
- anything. The callback is not fired.</p>
+ anything. The callback is not run.</p>
<li><p>Set the <a href=#entry-script>entry script</a> to be the <a href=#concept-script title=concept-script>script</a> being invoked.</li>
@@ -67271,8 +67275,8 @@
given task to one of the <a href=#task-queue title="task queue">task queues</a>
of the relevant <a href=#event-loop>event loop</a>. All the tasks from one
particular <dfn id=task-source>task source</dfn> (e.g. the callbacks generated by
- timers, the events dispatched for mouse movements, the tasks queued
- for the parser) must always be added to the same <a href=#task-queue>task
+ timers, the events fired for mouse movements, the tasks queued for
+ the parser) must always be added to the same <a href=#task-queue>task
queue</a>, but tasks from different <a href=#task-source title="task
source">task sources</a> may be placed in different <a href=#task-queue title="task queue">task queues</a>.</p>
@@ -67432,7 +67436,7 @@
document">inserted into the document</a>.</p>
<!--
- <p>Asynchronous mutation events must be dispatched using <span
+ <p>Asynchronous mutation events must be fired using <span
title="concept-task">tasks</span> <span title="queue a
task">queued</span> with the <span>DOM manipulation task
source</span>. <a href="#refsDOMEVENTS">[DOMEVENTS]</a></p>
@@ -67447,7 +67451,7 @@
<p>This <a href=#task-source>task source</a> is used for features that react
to user interaction, for example keyboard or mouse input.</p>
- <p>Asynchronous events sent in response to user input (e.g. <code title=event-click><a href=#event-click>click</a></code> events) must be dispatched using
+ <p>Asynchronous events sent in response to user input (e.g. <code title=event-click><a href=#event-click>click</a></code> events) must be fired using
<a href=#concept-task title=concept-task>tasks</a> <a href=#queue-a-task title="queue a
task">queued</a> with the <a href=#user-interaction-task-source>user interaction task
source</a>. <a href=#refsDOMEVENTS>[DOMEVENTS]</a></p>
@@ -67836,7 +67840,7 @@
</div>
- <p class=note><a href=#event-handlers>Event handlers</a> <span class=impl>therefore</span> always fire before event listeners
+ <p class=note><a href=#event-handlers>Event handlers</a> <span class=impl>therefore</span> always run before event listeners
attached using <code title=dom-EventTarget-addEventListener>addEventListener()</code>.</p>
<div class=impl>
@@ -68043,16 +68047,16 @@
<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>, which does not bubble (except where otherwise
stated) and is not cancelable (except where otherwise stated), and
- which uses the <code><a href=#event>Event</a></code> interface, must be dispatched at
- the given target.</p>
+ which uses the <code><a href=#event>Event</a></code> interface, must be created and
+ dispatched at the given target.</p>
<p><dfn id=fire-a-synthetic-mouse-event title="fire a synthetic mouse event">Firing a synthetic
mouse event named <var title="">e</var></dfn> means that an event
with the name <var title="">e</var>, which does not bubble (except
where otherwise stated) and is not cancelable (except where
otherwise stated), and which uses the <code><a href=#mouseevent>MouseEvent</a></code>
- interface, must be dispatched at the given target. The event object
- must have its <code title="">screenX</code>, <code title="">screenY</code>, <code title="">clientX</code>, <code title="">clientY</code>, and <code title="">button</code> attributes
+ interface, must be created and dispatched at the given target. The
+ event object must have its <code title="">screenX</code>, <code title="">screenY</code>, <code title="">clientX</code>, <code title="">clientY</code>, and <code title="">button</code> attributes
set to 0, its <code title="">ctrlKey</code>, <code title="">shiftKey</code>, <code title="">altKey</code>, and <code title="">metaKey</code> attributes set according to the current
state of the key input device, if any (false for any keys that are
not available), its <code title="">detail</code> attribute set to 1,
@@ -68396,7 +68400,7 @@
</dd>
- </dl><p class=note>This API does not guarantee that timers will fire
+ </dl><p class=note>This API does not guarantee that timers will run
exactly on schedule. Delays due to CPU load, other tasks, etc, are
to be expected.</p>
@@ -71424,7 +71428,7 @@
</dd>
</dl><p><code><a href=#datatransfer>DataTransfer</a></code> objects are used during the <a href=#dndevents>drag-and-drop events</a>, and are only valid while
- those events are being dispatched.</p>
+ those events are being fired.</p>
<div class=impl>
@@ -75038,7 +75042,7 @@
<p>When a message sent in this manner from the other peer is
received, a <code title=event-stream-message><a href=#event-stream-message>message</a></code>
- event is dispatched at the <code><a href=#peerconnection>PeerConnection</a></code> object.</p>
+ event is fired at the <code><a href=#peerconnection>PeerConnection</a></code> object.</p>
<p>The maximum length of <var title="">text</var> is 504 bytes
after encoding the string as UTF-8; attempting to send a payload
@@ -75056,7 +75060,7 @@
<p>When the other peer starts sending a stream in this manner, an
<code title=event-stream-addstream><a href=#event-stream-addstream>addstream</a></code>
- event is dispatched at the <code><a href=#peerconnection>PeerConnection</a></code> object.</p>
+ event is fired at the <code><a href=#peerconnection>PeerConnection</a></code> object.</p>
</dd>
@@ -75068,7 +75072,7 @@
<p>When the other peer stops sending a stream in this manner, a
<code title=event-stream-removestream><a href=#event-stream-removestream>removestream</a></code>
- event is dispatched at the <code><a href=#peerconnection>PeerConnection</a></code> object.</p>
+ event is fired at the <code><a href=#peerconnection>PeerConnection</a></code> object.</p>
</dd>
@@ -75938,7 +75942,8 @@
<p><dfn id=fire-a-stream-event title="fire a stream event">Firing a stream event named <var title="">e</var></dfn> with a <code><a href=#stream>Stream</a></code> <var title="">stream</var> means that an event with the name <var title="">e</var>, which does not bubble (except where otherwise
stated) and is not cancelable (except where otherwise stated), and
- which uses the <code><a href=#streamevent>StreamEvent</a></code> interface with the <code title=dom-StreamEvent-stream><a href=#dom-streamevent-stream>stream</a></code> attribute set to <var title="">stream</var>, must be dispatched at the given target.</p>
+ which uses the <code><a href=#streamevent>StreamEvent</a></code> interface with the <code title=dom-StreamEvent-stream><a href=#dom-streamevent-stream>stream</a></code> attribute set to <var title="">stream</var>, must be created and dispatched at the given
+ target.</p>
</div>
@@ -75951,7 +75956,7 @@
<table><thead><tr><th>Event name
<th>Interface
- <th>Dispatched when...
+ <th>Fired when...
<tbody><tr><td><dfn id=event-stream-ended title=event-stream-ended><code>ended</code></dfn>
<td><code><a href=#event>Event</a></code>
@@ -75961,7 +75966,7 @@
<table><thead><tr><th>Event name
<th>Interface
- <th>Dispatched when...
+ <th>Fired when...
<tbody><tr><td><dfn id=event-stream-connecting title=event-stream-connecting><code>connecting</code></dfn>
<td><code><a href=#event>Event</a></code>
Modified: source
===================================================================
--- source 2011-06-03 22:58:09 UTC (rev 6187)
+++ source 2011-06-04 00:46:45 UTC (rev 6188)
@@ -1817,13 +1817,14 @@
operate on the actual underlying data, not a snapshot of the
data.</p>
- <p>The terms <dfn title="">fire</dfn> and <dfn
- title="">dispatch</dfn> are used interchangeably in the context of
- events, as in the DOM Events specifications. The term <dfn
- title="concept-events-trusted">trusted event</dfn> is used as
- defined by the DOM Events specification. <!--
- http://krijnhoetmer.nl/irc-logs/webapps/20091218 --> <a
- href="#refsDOMEVENTS">[DOMEVENTS]</a></p>
+ <p>In the contexts of events, the terms <dfn title="">fire</dfn> and
+ <dfn title="">dispatch</dfn> are used as defined in the DOM Core
+ specification: firing an event means to create and dispatch it, and
+ dispatching an event means to follow the steps that propagate the
+ event through the tree. The term <dfn
+ title="concept-events-trusted">trusted event</dfn> is used to refer
+ to events that have the <span>trusted flag</span> set. <a
+ href="#refsDOMCORE">[DOMCORE]</a></p>
<h4>Plugins</h4>
@@ -7425,7 +7426,7 @@
returned. If, on the other hand, it fails or returns an out of range
value, or if the attribute is absent, the default value must be
returned instead, or −1 if there is no default value. On
- setting, if the value is negative, the user agent must fire an
+ setting, if the value is negative, the user agent must throw an
<code>INDEX_SIZE_ERR</code> exception. Otherwise, the given value
must be converted to the shortest possible string representing the
number as a <span>valid non-negative integer</span> and then that
@@ -7459,7 +7460,7 @@
fails or returns an out of range value, or if the attribute is
absent, the default value must be returned instead, or 1 if there is
no default value. On setting, if the value is zero, the user agent
- must fire an <code>INDEX_SIZE_ERR</code> exception. Otherwise, the
+ must throw an <code>INDEX_SIZE_ERR</code> exception. Otherwise, the
given value must be converted to the shortest possible string
representing the number as a <span>valid non-negative integer</span>
and then that string must be used as the new content attribute
@@ -18168,13 +18169,13 @@
elements</span>.</p>
<p class="example">Thus, for example, a bubbling <code
- title="event-error">error</code> event fired on a child of <span>the
- body element</span> of a <code>Document</code> would first trigger
- the <code title="handler-onerror">onerror</code> <span>event handler
- content attributes</span> of that element, then that of the root
- <code>html</code> element, and only <em>then</em> would it trigger
- the <code title="handler-window-onerror">onerror</code> <span
- title="event handler content attributes">event handler content
+ title="event-error">error</code> event dispatched on a child of
+ <span>the body element</span> of a <code>Document</code> would first
+ trigger the <code title="handler-onerror">onerror</code> <span>event
+ handler content attributes</span> of that element, then that of the
+ root <code>html</code> element, and only <em>then</em> would it
+ trigger the <code title="handler-window-onerror">onerror</code>
+ <span title="event handler content attributes">event handler content
attribute</span> on the <code>body</code> element. This is because
the event would bubble from the target, to the <code>body</code>, to
the <code>html</code>, to the <code>Document</code>, to the
@@ -18182,7 +18183,7 @@
handler</span> on the <code>body</code> is watching the
<code>Window</code> not the <code>body</code>. A regular event
listener attached to the <code>body</code> using <code
- title="">addEventListener()</code>, however, would fire when the
+ title="">addEventListener()</code>, however, would be run when the
event bubbled through the <code>body</code> and not when it reaches
the <code>Window</code> object.</p>
@@ -30260,7 +30261,7 @@
ended</span>, because there is always the chance the user will
seek back to the start. In fact, in this situation, once <span
title="ended playback">playback has ended</span>, the user agent
- will end up dispatching a <code
+ will end up firing a <code
title="event-media-stalled">stalled</code> event, as described
earlier.</p>
@@ -37429,7 +37430,7 @@
<tr>
<th>Event name
<th>Interface
- <th>Dispatched when...
+ <th>Fired when...
<th>Preconditions
<tbody>
@@ -37564,7 +37565,7 @@
<tr>
<th>Event name
<th>Interface
- <th>Dispatched when...
+ <th>Fired when...
<tbody>
<tr>
@@ -42702,12 +42703,13 @@
</ol>
- <p>Mouse clicks on an image associated with a set of layered shapes
- per the above algorithm must be dispatched to the top-most shape
- covering the point that the pointing device indicated (if any), and
- then, must be dispatched again (with a new <code>Event</code>
- object) to the image element itself. User agents may also allow
- individual <code>area</code> elements representing <span
+ <p>Pointing device interaction with an image associated with a set
+ of layered shapes per the above algorithm must result in the
+ relevant user interaction events being first fired to the top-most
+ shape covering the point that the pointing device indicated (if
+ any), and then fired again (with a new <code>Event</code> object) to
+ the image element itself. User agents may also allow individual
+ <code>area</code> elements representing <span
title="hyperlink">hyperlinks</span> to be selected and activated
(e.g. using a keyboard); events from this are not also propagated to
the image.</p>
@@ -59811,14 +59813,14 @@
<dt>If the user requested a context menu using a pointing device</dt>
- <dd><p>The user agent must dispatch an event with the name <code
+ <dd><p>The user agent must fire an event with the name <code
title="event-contextmenu">contextmenu</code>, that bubbles and is
cancelable, and that uses the <code>MouseEvent</code> interface, at
the element for which the menu was requested. The context
information of the event must be set to the same values as the last
- <code>MouseEvent</code> user interaction event that was dispatched
- as part of the gesture that that was interpreted as a request for
- the context menu.</p></dd>
+ <code>MouseEvent</code> user interaction event that was fired as
+ part of the gesture that that was interpreted as a request for the
+ context menu.</p></dd>
<dt>Otherwise</dt>
@@ -73804,7 +73806,7 @@
<tr>
<th> Event name
<th> Interface
- <th> Dispatched when...
+ <th> Fired when...
<th> Next events
<tbody>
<tr>
@@ -76439,7 +76441,7 @@
<li><p>If the <span>script's global object</span> is a
<code>Window</code> object whose <code>Document</code> object is
not <span>fully active</span>, then abort these steps without doing
- anything. The callback is not fired.</p>
+ anything. The callback is not run.</p>
<li><p>Set the <span>entry script</span> to be the <span
title="concept-script">script</span> being invoked.</p></li>
@@ -76748,8 +76750,8 @@
given task to one of the <span title="task queue">task queues</span>
of the relevant <span>event loop</span>. All the tasks from one
particular <dfn>task source</dfn> (e.g. the callbacks generated by
- timers, the events dispatched for mouse movements, the tasks queued
- for the parser) must always be added to the same <span>task
+ timers, the events fired for mouse movements, the tasks queued for
+ the parser) must always be added to the same <span>task
queue</span>, but tasks from different <span title="task
source">task sources</span> may be placed in different <span
title="task queue">task queues</span>.</p>
@@ -76944,7 +76946,7 @@
document">inserted into the document</span>.</p>
<!--
- <p>Asynchronous mutation events must be dispatched using <span
+ <p>Asynchronous mutation events must be fired using <span
title="concept-task">tasks</span> <span title="queue a
task">queued</span> with the <span>DOM manipulation task
source</span>. <a href="#refsDOMEVENTS">[DOMEVENTS]</a></p>
@@ -76960,7 +76962,7 @@
to user interaction, for example keyboard or mouse input.</p>
<p>Asynchronous events sent in response to user input (e.g. <code
- title="event-click">click</code> events) must be dispatched using
+ title="event-click">click</code> events) must be fired using
<span title="concept-task">tasks</span> <span title="queue a
task">queued</span> with the <span>user interaction task
source</span>. <a href="#refsDOMEVENTS">[DOMEVENTS]</a></p>
@@ -77415,7 +77417,7 @@
</div>
<p class="note"><span>Event handlers</span> <span
- class="impl">therefore</span> always fire before event listeners
+ class="impl">therefore</span> always run before event listeners
attached using <code
title="dom-EventTarget-addEventListener">addEventListener()</code>.</p>
@@ -77659,16 +77661,16 @@
title="">e</var></dfn> means that an event with the name <var
title="">e</var>, 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>
+ which uses the <code>Event</code> interface, must be created and
+ dispatched at the given target.</p>
<p><dfn title="fire a synthetic mouse event">Firing a synthetic
mouse event named <var title="">e</var></dfn> means that an event
with the name <var title="">e</var>, which does not bubble (except
where otherwise stated) and is not cancelable (except where
otherwise stated), and which uses the <code>MouseEvent</code>
- interface, must be dispatched at the given target. The event object
- must have its <code title="">screenX</code>, <code
+ interface, must be created and dispatched at the given target. The
+ event object must have its <code title="">screenX</code>, <code
title="">screenY</code>, <code title="">clientX</code>, <code
title="">clientY</code>, and <code title="">button</code> attributes
set to 0, its <code title="">ctrlKey</code>, <code
@@ -78064,7 +78066,7 @@
</dl>
- <p class="note">This API does not guarantee that timers will fire
+ <p class="note">This API does not guarantee that timers will run
exactly on schedule. Delays due to CPU load, other tasks, etc, are
to be expected.</p>
@@ -81531,7 +81533,7 @@
<p><code>DataTransfer</code> objects are used during the <a
href="#dndevents">drag-and-drop events</a>, and are only valid while
- those events are being dispatched.</p>
+ those events are being fired.</p>
<div class="impl">
@@ -85793,7 +85795,7 @@
<p>When a message sent in this manner from the other peer is
received, a <code title="event-stream-message">message</code>
- event is dispatched at the <code>PeerConnection</code> object.</p>
+ event is fired at the <code>PeerConnection</code> object.</p>
<p>The maximum length of <var title="">text</var> is 504 bytes
after encoding the string as UTF-8; attempting to send a payload
@@ -85811,7 +85813,7 @@
<p>When the other peer starts sending a stream in this manner, an
<code title="event-stream-addstream">addstream</code>
- event is dispatched at the <code>PeerConnection</code> object.</p>
+ event is fired at the <code>PeerConnection</code> object.</p>
</dd>
@@ -85824,7 +85826,7 @@
<p>When the other peer stops sending a stream in this manner, a
<code
title="event-stream-removestream">removestream</code>
- event is dispatched at the <code>PeerConnection</code> object.</p>
+ event is fired at the <code>PeerConnection</code> object.</p>
</dd>
@@ -86865,7 +86867,8 @@
stated) and is not cancelable (except where otherwise stated), and
which uses the <code>StreamEvent</code> interface with the <code
title="dom-StreamEvent-stream">stream</code> attribute set to <var
- title="">stream</var>, must be dispatched at the given target.</p>
+ title="">stream</var>, must be created and dispatched at the given
+ target.</p>
</div>
@@ -86881,7 +86884,7 @@
<tr>
<th>Event name
<th>Interface
- <th>Dispatched when...
+ <th>Fired when...
<tbody>
<tr>
@@ -86899,7 +86902,7 @@
<tr>
<th>Event name
<th>Interface
- <th>Dispatched when...
+ <th>Fired when...
<tbody>
@@ -87972,8 +87975,8 @@
worker.</p>
<p>When the user agent is to <dfn>fire a worker error event</dfn> at
- a <code>Worker</code> object, it must dispatch an event that uses
- the <code>ErrorEvent</code> interface, with the name <code
+ a <code>Worker</code> object, it must create and dispatch an event
+ that uses the <code>ErrorEvent</code> interface, with the name <code
title="event-error">error</code>, that doesn't bubble and is
cancelable, with its <code
title="dom-ErrorEvent-message">message</code>, <code
@@ -87984,8 +87987,8 @@
that worker is also a dedicated worker, then the user agent must
again <span>queue a task</span> to <span>fire a worker error
event</span> at the <code>Worker</code> object associated with
- <em>that</em> worker. Otherwise, then the error may be reported
- to the user.</p>
+ <em>that</em> worker. Otherwise, then the error may be reported to
+ the user.</p>
<p>The <span>task source</span> for the tasks mentioned above is the
<span>DOM manipulation task source</span>.</p>
More information about the Commit-Watchers
mailing list