W3C home > Mailing lists > Public > public-html-commits@w3.org > November 2012

html5/workers Overview.html,1.346,1.347

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Mon, 05 Nov 2012 21:38:25 +0000
To: public-html-commits@w3.org
Message-Id: <E1TVUNF-0008Tv-9Q@lionel-hutz.w3.org>
Update of /sources/public/html5/workers
In directory hutz:/tmp/cvs-serv32589

Modified Files:
	Overview.html 
Log Message:
Try to be more normatively tight about 'fire' and 'dispatch'. (whatwg r7506)

Index: Overview.html
===================================================================
RCS file: /sources/public/html5/workers/Overview.html,v
retrieving revision 1.346
retrieving revision 1.347
diff -u -d -r1.346 -r1.347
--- Overview.html	25 Oct 2012 18:10:47 -0000	1.346
+++ Overview.html	5 Nov 2012 21:38:22 -0000	1.347
@@ -216,7 +216,7 @@
 
    <h1>Web Workers</h1>
    
-   <h2 class="no-num no-toc" id="editor-s-draft-25-october-2012">Editor's Draft 25 October 2012</h2>
+   <h2 class="no-num no-toc" id="editor-s-draft-5-november-2012">Editor's Draft 5 November 2012</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>
@@ -353,7 +353,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 25 October 2012 Editor's Draft.
+  This specification is the 5 November 2012 Editor's Draft.
   </p>
 
   
@@ -1845,16 +1845,15 @@
   
   </p>
 
-  <p>For dedicated workers, if the error is still <i title="concept-error-nothandled">not handled</i> afterwards, or if
-  the error occurred while handling a previous script error, the user
-  agent must <span>queue a task</span> to fire 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>, <code title="dom-ErrorEvent-lineno"><a href="#dom-errorevent-lineno">lineno</a></code>, and <code title="dom-ErrorEvent-column"><a href="#dom-errorevent-column">column</a></code> attributes initialized
-  appropriately, at the <code><a href="#worker">Worker</a></code> object associated with the
-  worker. If the event is not canceled, the user agent must act as if
-  the uncaught runtime script error had occurred in the global scope
-  that the <code><a href="#worker">Worker</a></code> object is in, thus repeating the entire
-  runtime script error reporting process one level up.</p>
+  <p>For dedicated workers, if the error is still <i title="concept-error-nothandled">not
+  handled</i> afterwards, or if the error occurred while handling a previous script error, the user
+  agent must <span>queue a task</span> to <span title="concept-event-fire">fire</span> a <span title="concept-events-trusted">trusted</span> 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>, <code title="dom-ErrorEvent-lineno"><a href="#dom-errorevent-lineno">lineno</a></code>, and <code title="dom-ErrorEvent-column"><a href="#dom-errorevent-column">column</a></code>
+  attributes initialized appropriately, at the <code><a href="#worker">Worker</a></code> object associated with the
+  worker. If the event is not canceled, the user agent must act as if the uncaught runtime script
+  error had occurred in the global scope that the <code><a href="#worker">Worker</a></code> object is in, thus repeating
+  the entire runtime script error reporting process one level up.</p>
 
   <p>If the implicit port connecting the worker to its
   <code><a href="#worker">Worker</a></code> object has been disentangled (i.e. if the parent
@@ -2223,7 +2222,8 @@
        is initialized to the empty string, has a <code title="dom-MessageEvent-ports">ports</code>
        attribute whose value is initialized to a <span title="dfn-read-only-array">read only</span>
        array containing only the newly created port, and has a <code title="dom-MessageEvent-source">source</code> attribute whose value is initialized to the
-       newly created port, and <span>queue a task</span> to dispatch the event at <var title="">worker global scope</var>.</li>
+       newly created port, and <span>queue a task</span> to <span title="concept-event-dispatch">dispatch</span> the event at <var title="">worker global
+       scope</var>.</li>
 
        <li>
 
@@ -2278,8 +2278,8 @@
    string, has a <code title="dom-MessageEvent-ports">ports</code> attribute whose value is
    initialized to a <span title="dfn-read-only-array">read only</span> array containing only the
    newly created port, and has a <code title="dom-MessageEvent-source">source</code> attribute whose
-   value is initialized to the newly created port, and <span>queue a task</span> to dispatch the
-   event at <var title="">worker global scope</var>.</li>
+   value is initialized to the newly created port, and <span>queue a task</span> to <span title="concept-event-dispatch">dispatch</span> the event at <var title="">worker global
+   scope</var>.</li>
 
    <li>
 
Received on Monday, 5 November 2012 21:38:26 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 5 November 2012 21:38:26 GMT