W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2011

Re: WebApps-ISSUE-181 (FileError-Name): Use case for FileError and FileException name attribute [File API]

From: Arun Ranganathan <arun@mozilla.com>
Date: Tue, 21 Jun 2011 12:36:47 -0400
Message-ID: <4E00C89F.3090600@mozilla.com>
To: Web Applications Working Group WG <public-webapps@w3.org>
> Web Applications Working Group Issue Tracker:
>> FileError [1] and FileException [2] both define a DOMString attribute
>> called name that contains the name of the error/exception constant as
>> a string. Since this is not a useful "human readable" error message,
>> and developers should be encouraged to write code that compares
>> against the code attribute, it's not clear what the purpose of 'name'
>> is. We'd prefer to remove it.
> Web IDL specifies that exceptions in ECMAScript will have a name
> property on their prototype whose value is the identifier of the
> interface.  If name is removed from FileException (and
> OperationNotAllowedException, which I also would recommend), then you
> will have `aFileException.name == "FileException"`.
I'll make this change in keeping with WebIDL and ECMAScript.

-- A*
Received on Tuesday, 21 June 2011 16:37:16 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:20 UTC