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

Re: [IndexedDB] blocked event could be an error

From: Jonas Sicking <jonas@sicking.cc>
Date: Wed, 5 Sep 2012 14:38:32 -0700
Message-ID: <CA+c2ei9HNcNOrJKM3Ckko_2d0yRcF=dmTDQ0vMtOpMA=E1vzxw@mail.gmail.com>
To: Odin HÝrthe Omdal <odinho@opera.com>
Cc: public-webapps@w3.org
On Wed, Sep 5, 2012 at 9:54 AM, Odin HÝrthe Omdal <odinho@opera.com> wrote:
> David Grogan <dgrogan@chromium.org> wrote:
>
>> Odin wrote:
>>>
>>> Also, there's a much bigger chance of developers listening to error on
>>> the opening page, rather than blocked.
>>
>>
>> +1. Replacing "blocked" event with an "error" event named BlockedError
>> would be an improvement.
>
>
> I did this. Proposed patch to the spec is here:
>
>       http://odinho.html5.org/IndexedDB/spec/blocked.patch
>
>
> If you are not super proficient reading patches but prefer to see the
> result, I have the file I used to produce the diff here:
>
>       http://odinho.html5.org/IndexedDB/spec/Overview.html

Like I said, I think it's too late to make such a big change. I
believe it's much too late to make such a change in IE10, and we have
been shipping Firefox with the current behavior for quite a while now
(and are about to unprefix with our current behavior).

/ Jonas
Received on Wednesday, 5 September 2012 21:39:30 GMT

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