W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2010

Re: File API exception codes

From: Eric Uhrhane <ericu@google.com>
Date: Tue, 14 Sep 2010 16:51:06 -0700
Message-ID: <AANLkTi=TfWMrusOz7AY9i+H5BkT9Vcm+J5DU7w54g-q=@mail.gmail.com>
To: Arun Ranganathan <aranganathan@mozilla.com>
Cc: Ian Hickson <ian@hixie.ch>, public-webapps@w3.org, Anne van Kesteren <annevk@opera.com>
On Thu, Sep 9, 2010 at 6:39 AM, Arun Ranganathan
<aranganathan@mozilla.com> wrote:
> ----- Original Message -----
>> On Wed, Sep 8, 2010 at 12:43 AM, Anne van Kesteren <annevk@opera.com>
>> wrote:
>
>> >
>> > That works for me too, but then please use internally consistent
>> > numbering
>> > rather than some codes matching DOMException and the new codes not
>> > matching
>> > DOMException as that is just too confusing, especially going
>> > forward. I.e.
>> > DOMException might gain a similar exception but it will have a
>> > different
>> > number, so only for the older numbers it will match, etc. It just
>> > does not
>> > make much sense.
>>
>> OK, so we stick with the current interfaces, but try to keep the
>> numbers all matching/nonconflicting. Works for me.
>
> OK, we'll use in-order numbering and not have any kind of dependency on DOMException.

Sorry, I misread the conclusion.  In-order numbering does make more
sense.  Let me know when you're about to update your numbering, and
I'll fix mine to go with them.
Received on Tuesday, 14 September 2010 23:51:57 GMT

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