New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 270005 link

Starred by 1 user

Issue metadata

Status: Fixed
OOO until 4th
Closed: Oct 2013
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug

Blocked on:
issue 269538

Sign in to add a comment

Add the 'error' property to Workers' 'onerror' handler.

Project Member Reported by, Aug 8 2013

Issue description  added support for the 'error' property in page's 'window.onerror' handler. We should support the same for 'self.onerror' in Workers.

Note that we should _not_, however, propagate the error object outside of the Worker into the page-level handler.

Doing anything here relies first upon getting the sanitization right, which is covered in .
Project Member

Comment 1 by, Aug 12 2013

The following revision refers to this bug:

r155953 | | 2013-08-12T21:27:16.989378Z

Changed paths:

Add 'error' property to exceptions thrown via Worker::importScripts.

If an imported script throws an exception, and the script is same-origin
with the Worker, we should provide the exception object when handling
the exception via 'self.onerror'. The exception should not, however, be
available to the page-level 'window.onerror' (we'd be leaking state
across worlds otherwise (also, the spec says not to[1])).

This patch pulls the logic governing the exception object's storage
(wrapping the ErrorEvent, storing the value on a hidden property) out of
V8Initializer, and moves it to a static method on V8ErrorHandler so that
it's easily reusable inside WorkerScriptController.


BUG= 270005 

Review URL:

Comment 2 by, Oct 14 2013

Status: Fixed

Sign in to add a comment