W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2011

Re: [File API] Issue 182 about OperationNotAllowed

From: Jonas Sicking <jonas@sicking.cc>
Date: Tue, 4 Oct 2011 01:37:41 -0700
Message-ID: <CA+c2ei_sj9Bfh=r4wOLVyO7Dis-+ic5iaMo_nUqCMXe-JxGscw@mail.gmail.com>
To: Anne van Kesteren <annevk@opera.com>
Cc: arun@mozilla.com, Adrian Bateman <adrianba@microsoft.com>, Arthur Barstow <art.barstow@nokia.com>, Jonas Sicking <sicking@mozilla.com>, public-webapps <public-webapps@w3.org>
On Mon, Oct 3, 2011 at 11:54 PM, Anne van Kesteren <annevk@opera.com> wrote:
> On Tue, 04 Oct 2011 00:59:18 +0200, Jonas Sicking <jonas@sicking.cc> wrote:
>> Yup. I do wonder if we should introduce a DOMError class which can be
>> reused in various cases which need APIs like this. IndexedDB could
>> also use it and I seem to recall that HTML5 does too.
> I could certainly introduce a DOMError interface with a name and a message
> attribute. For the APIs that want to provide the same information
> asynchronous as they do synchronous through exceptions that makes sense.
> Would that work?

Yup, that'd work.

Another option which just occurred to me is to actually use
DOMException objects. The ECMAScript error objects don't actually have
anything "exception specific" about them. DOMException only does so by
name of the interface.

Either way is fine with me.

/ Jonas
Received on Tuesday, 4 October 2011 08:44:41 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:36 UTC