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

Re: [indexeddb] Change IDBRequest.errorCode property to match new Exception type model

From: Jonas Sicking <jonas@sicking.cc>
Date: Mon, 3 Oct 2011 19:31:18 -0700
Message-ID: <CA+c2ei_6o1FSLw9QsBS8zN8upyX=O_AoufaDpwEeVK=i0W2HsQ@mail.gmail.com>
To: Israel Hilerio <israelh@microsoft.com>
Cc: "public-webapps@w3.org" <public-webapps@w3.org>
On Mon, Oct 3, 2011 at 5:36 PM, Israel Hilerio <israelh@microsoft.com> wrote:
> Jonas,
>
> We’re removing error code values as part of the new exception type model.
> This will impact the IDBRequest.errorCode property.  I believe we want to
> rename this property to errorName and change its type to DOMString in order
> to match the new Exception type model name. This change will impact all the
> places where errorCode is used today in the spec.  However, it should be
> fairly easy to fix assuming we follow the above model.
>
> Do you agree?

We might want to do something similar to what the FileAPI spec is
doing, and the HTML5 spec is doing for HTMLMediaElement. Both specs
have a .error property which returns an object which contains error
information. A nice aspect of that approach is that it enables us to
add more information about the error later, and even have different
pieces of information for different errors.

/ Jonas
Received on Tuesday, 4 October 2011 02:32:15 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:48 GMT