workers; hixie: Update 'fire' and 'dispatch' terminology. (whatwg r6188)

workers; hixie: Update 'fire' and 'dispatch' terminology. (whatwg r6188)

http://dev.w3.org/cvsweb/html5/workers/Overview.html?r1=1.287&r2=1.288&f=h
http://html5.org/tools/web-apps-tracker?from=6187&to=6188

===================================================================
RCS file: /sources/public/html5/workers/Overview.html,v
retrieving revision 1.287
retrieving revision 1.288
diff -u -d -r1.287 -r1.288
--- Overview.html 1 Jun 2011 17:43:37 -0000 1.287
+++ Overview.html 4 Jun 2011 00:47:26 -0000 1.288
@@ -211,7 +211,7 @@
 
    <h1>Web Workers</h1>
    
-   <h2 class="no-num no-toc" id="editor-s-draft-1-june-2011">Editor's Draft 1 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/workers/">http://www.w3.org/TR/workers/</a></dd>
     <dt>Latest Editor's Draft:</dt>
@@ -316,7 +316,7 @@
   </dl><p>The W3C <a href="http://www.w3.org/2008/webapps/">Web Applications
   Working Group</a> is the W3C working group responsible for this
   specification's progress along the W3C Recommendation track.
-  This specification is the 1 June 2011 Editor's Draft.
+  This specification is the 4 June 2011 Editor's Draft.
   </p><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5
   February 2004 W3C Patent Policy</a>. W3C maintains a <a href="http://www.w3.org/2004/01/pp-impl/42538/status" rel="disclosure">public list of
   any patent disclosures</a> made in connection with the deliverables
@@ -1349,16 +1349,16 @@
   agent must <span>queue a task</span> 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 the
   worker.<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 <span>queue a task</span> 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>The <span>task source</span> for the tasks mentioned above is the
+  <em>that</em> worker. Otherwise, then the error may be reported to
+  the user.<p>The <span>task source</span> for the tasks mentioned above is the
   <span>DOM manipulation task source</span>.<hr><pre class="idl">interface <dfn id="errorevent">ErrorEvent</dfn> : <span>Event</span> {
   readonly attribute DOMString <a href="#dom-errorevent-message" title="dom-ErrorEvent-message">message</a>;
   readonly attribute DOMString <a href="#dom-errorevent-filename" title="dom-ErrorEvent-filename">filename</a>;

Received on Friday, 17 June 2011 09:54:46 UTC