W3C home > Mailing lists > Public > whatwg@whatwg.org > February 2010

[whatwg] Structured clone for an Error object

From: ATSUSHI TAKAYAMA <taka.atsushi@googlemail.com>
Date: Sun, 28 Feb 2010 17:03:31 -0500
Message-ID: <9cef076f1002281403y19b5e63aqa6eb02d70760f7b1@mail.gmail.com>
On Fri, Feb 26, 2010 at 1:44 PM, Drew Wilson <atwilson at google.com> wrote:
> BTW, the spec says that unhandled exceptions are either propagated to the
> parent Worker object (in the case of dedicated workers) or reported to the
> user via the console (for shared workers).
> So I'm not certain why passing Error objects via postMessage() would be
> necessary for a spec-compliant UA (note that some UAs have bugs in their
> implementation such that not all exceptions in Workers are logged to the
> console, but that shouldn't motivate a change in the spec).
> -atw

This is good to know. As far as I tested, Firefox and Safari actually
supports worker.onerror.

It also turns out that Firefox and Chromium actually sends a clone of
an Error object. Safari turns it into a string. Are they going to
convert change the behavior in the future?

Received on Sunday, 28 February 2010 14:03:31 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:21 UTC