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: Thu, 26 Jul 2012 15:31:08 -0700
Message-ID: <CA+c2ei9a5tpC3yP_neX5bcP==VYuVPjYjJdAk0zK-qofSzQGnQ@mail.gmail.com>
To: Joćo Eiras <joaoe@opera.com>
Cc: public-webapps@w3.org
On Thu, Jul 26, 2012 at 3:28 PM, Joćo Eiras <joaoe@opera.com> wrote:
>> I definitely think that we need to keep the "blocked" events as
>> non-error events since it supports the use case of opening a
>> connection and displaying UI to the user asking that other tabs are
>> closed if the "blocked" event fires.
> That can very well be achieved by detecting the BlockedError, and adding a
> retry button which calls open() again.
> If you really want a open() and wait forever behavior, that should not be
> the default one.

I'm not at all comfortable with changing the default behavior this
late in the process.

/ Jonas
Received on Thursday, 26 July 2012 22:32:05 UTC

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