- From: poot <cvsmail@w3.org>
- Date: Fri, 17 Jun 2011 05:54:45 -0400
- To: public-html-diffs@w3.org
hixie: Update 'fire' and 'dispatch' terminology. (whatwg r6188)
http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.4960&r2=1.4961&f=h
http://html5.org/tools/web-apps-tracker?from=6187&to=6188
===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.4960
retrieving revision 1.4961
diff -u -d -r1.4960 -r1.4961
--- Overview.html 3 Jun 2011 22:58:15 -0000 1.4960
+++ Overview.html 4 Jun 2011 00:46:55 -0000 1.4961
@@ -318,7 +318,7 @@
<h1>HTML5</h1>
<h2 class="no-num no-toc" id="a-vocabulary-and-associated-apis-for-html-and-xhtml">A vocabulary and associated APIs for HTML and XHTML</h2>
- <h2 class="no-num no-toc" id="editor-s-draft-3-june-2011">Editor's Draft 3 June 2011</h2>
+ <h2 class="no-num no-toc" id="editor-s-draft-4-june-2011">Editor's Draft 4 June 2011</h2>
<dl><dt>Latest Published Version:</dt>
<dd><a href="http://www.w3.org/TR/html5/">http://www.w3.org/TR/html5/</a></dd>
<dt>Latest Editor's Draft:</dt>
@@ -464,7 +464,7 @@
Group</a> is the W3C working group responsible for this
specification's progress along the W3C Recommendation
track.
- This specification is the 3 June 2011 Editor's Draft.
+ This specification is the 4 June 2011 Editor's Draft.
</p><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><p>Work on this specification is also done at the <a href="http://www.whatwg.org/">WHATWG</a>. The W3C HTML working group
actively pursues convergence with the WHATWG, as required by the <a href="http://www.w3.org/2007/03/HTML-WG-charter">W3C HTML working
group charter</a>.</p><!-- UNDER NO CIRCUMSTANCES IS THE FOLLOWING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5
@@ -2459,9 +2459,12 @@
it.<p>If a DOM object is said to be <dfn id="live">live</dfn>, then the
attributes and methods on that object <span class="impl">must</span>
operate on the actual underlying data, not a snapshot of the
- data.<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. <a href="#refsDOMEVENTS">[DOMEVENTS]</a><h4 id="plugins"><span class="secno">2.1.5 </span>Plugins</h4><p>The term <dfn id="plugin">plugin</dfn> refers to a user-agent defined set of
+ data.<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><h4 id="plugins"><span class="secno">2.1.5 </span>Plugins</h4><p>The term <dfn id="plugin">plugin</dfn> refers to a user-agent defined set of
content handlers used by the user agent that can take part in the
user agent's rendering of a <code><a href="#document">Document</a></code> object, but that
neither act as <a href="#child-browsing-context" title="child browsing context">child browsing
@@ -6490,7 +6493,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
@@ -6520,7 +6523,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
@@ -14143,19 +14146,20 @@
handlers</a> of the <code><a href="#window">Window</a></code> object, exposed on the
<code><a href="#the-body-element">body</a></code> element, shadow the generic <a href="#event-handlers">event
handlers</a> with the same names normally supported by <a href="#html-elements">HTML
- elements</a>.<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
+ elements</a>.<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.<div class="example">
@@ -23235,7 +23239,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>
@@ -26997,7 +27001,7 @@
</div><h5 id="mediaevents"><span class="secno">4.8.10.15 </span>Event summary</h5><p><i>This section is non-normative.</i><p>The following events fire on <a href="#media-element" title="media element">media
elements</a> as part of the processing model described above:<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>
@@ -27099,7 +27103,7 @@
<td>
</table><p>The following events fire on <code><a href="#mediacontroller">MediaController</a></code> objects:<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>
@@ -28206,12 +28210,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>
@@ -40577,13 +40582,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>
@@ -46610,7 +46615,7 @@
to the state of the cache update, so that the user can be notified
appropriately. The events are as follows:<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>
@@ -48718,7 +48723,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>
@@ -48970,8 +48975,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>
@@ -49135,7 +49140,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>
@@ -49441,7 +49446,7 @@
<code><a href="#function">Function</a></code> object associated with the event handler
otherwise.</p>
- </div><p class="note"><a href="#event-handlers">Event handlers</a> <span class="impl">therefore</span> always fire before event listeners
+ </div><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>.<div class="impl">
<p class="note">The <var title="dom-event-listener">listener</var>
@@ -49622,16 +49627,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,
@@ -49938,7 +49943,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.<div class="impl">
@@ -52542,7 +52547,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.<div class="impl">
+ those events are being fired.<div class="impl">
<p>A <code><a href="#datatransfer">DataTransfer</a></code> object is associated with a
<a href="#drag-data-store">drag data store</a> while it is valid.</p>
Received on Friday, 17 June 2011 09:54:52 UTC