Skip to content
Permalink
Browse files

[giow] (1) Make worker errors propagate all the way up to the Documen…

…t, hitting the global scope .onerror each step of the way. This isn't a great way to specify it but I couldn't work out a cleaner way that didn't involve major (potentially risky) surgery and inventing new terms. If it turns out that there are other things that'd need the parent/child infrastructure to be better defined I'll do it then.

Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=12067

git-svn-id: http://svn.whatwg.org/webapps@6263 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information...
Hixie committed Jun 21, 2011
1 parent 7e06737 commit 92f7e14844698fc8fbb211a90ace09359b6fd9a9
Showing with 48 additions and 32 deletions.
  1. +23 −16 complete.html
  2. +25 −16 source

<p>For dedicated workers, if the error is still <i title=concept-error-nothandled><a href=#concept-error-nothandled>not handled</a></i> afterwards, or if
the error occurred while handling a previous script error, the user
agent must <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 the
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 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
agent must <a href=#queue-a-task>queue a task</a> 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>, 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>

<p>The <a href=#task-source>task source</a> for the tasks mentioned above is the
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
worker has been terminated), then the user agent must act as if the
<code><a href=#worker>Worker</a></code> object had no <code title=event-error>error</code> event handler and as if that
worker's <code title=handler-WorkerGlobalScope-onerror><a href=#handler-workerglobalscope-onerror>onerror</a></code> attribute
was null, but must otherwise act as described above.</p>

<p class=note>Thus, error reports proagate up to the chain of
dedicated workers up to the original <code><a href=#document>Document</a></code>, even if
some of the workers along this chain have been terminated and
garbage collected.</p>

<p>The <a href=#task-source>task source</a> for the task mentioned above is the
<a href=#dom-manipulation-task-source>DOM manipulation task source</a>.</p>

<hr><pre class=idl>interface <dfn id=errorevent>ErrorEvent</dfn> : <a href=#event>Event</a> {





</div><!--data-component-->


41 source
<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>fire a worker error
event</span> at the <code>Worker</code> object associated with the
worker.</p>

<p>When the user agent is to <dfn>fire a worker error event</dfn> at
a <code>Worker</code> object, it must create and dispatch an event
that uses the <code>ErrorEvent</code> interface, with the name <code
agent must <span>queue a task</span> to fire 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
title="dom-ErrorEvent-filename">filename</code>, and <code
title="dom-ErrorEvent-lineno">lineno</code> attributes set
appropriately. The default action of this event depends on whether
the <code>Worker</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 <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>

<p>The <span>task source</span> for the tasks mentioned above is the
appropriately, at the <code>Worker</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>Worker</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>Worker</code> object has been disentangled (i.e. if the parent
worker has been terminated), then the user agent must act as if the
<code>Worker</code> object had no <code
title="event-error">error</code> event handler and as if that
worker's <code
title="handler-WorkerGlobalScope-onerror">onerror</code> attribute
was null, but must otherwise act as described above.</p>

<p class="note">Thus, error reports proagate up to the chain of
dedicated workers up to the original <code>Document</code>, even if
some of the workers along this chain have been terminated and
garbage collected.</p>

<p>The <span>task source</span> for the task mentioned above is the
<span>DOM manipulation task source</span>.</p>

<hr>
interface's <span>relevant namespace object</span> is a
<code>Window</code> object. <a href="#refsWEBIDL">[WEBIDL]</a></p>



<!--END workers-->
<!--END whatwg-workers-->

0 comments on commit 92f7e14

Please sign in to comment.
You can’t perform that action at this time.