Re: error handling from Martin Thomson on 2014-01-28 (public-orca@w3.org from January 2014)

From: Martin Thomson <martin.thomson@gmail.com>
Date: Tue, 28 Jan 2014 14:35:04 -0800
To: Justin Uberti <juberti@google.com>
Cc: "Adalberto Foresti (MS OPEN TECH)" <aforesti@microsoft.com>, Robin Raymond <robin@hookflash.com>, public-orca <public-orca@w3.org>
Message-ID: <CABkgnnUZD+pt7SRNWioP0WCcTtMwxO1gk6ypVXsrGgO_bKWd5w@mail.gmail.com>

On 28 January 2014 14:15, Justin Uberti <juberti@google.com> wrote:
> So while a 'failed' state may make sense, it may be better to simply have
> errors trigger a change to "closed" with an accompanying .onerror callback
> that surfaces a detailed error object.

That makes plenty of sense to me.  onerror seems like a general
pattern worth following.  Having more direct error reporting for
specific actions can still be useful, but I'd expect that with an
'onerror', the bar would be higher for adding secondary error
reporting channels.

Received on Tuesday, 28 January 2014 22:35:32 UTC