Re: [IndexedDB] setVersion blocked on uncollected garbage IDBDatabases from ben turner on 2011-02-08 (public-webapps@w3.org from January to March 2011)

From: ben turner <bent.mozilla@gmail.com>
Date: Tue, 8 Feb 2011 11:51:00 -0800
To: Jeremy Orlow <jorlow@chromium.org>
Cc: Jonas Sicking <jonas@sicking.cc>, João Eiras <joao.eiras@gmail.com>, public-webapps <public-webapps@w3.org>
Message-ID: <AANLkTimxpOSu67vTj-dSBddqM1a6tvoup-Ea+E4nRdGt@mail.gmail.com>

I'm actually fine with keeping the setVersion from proceeding until
the old database is collected. First, this is probably a bug in the
web page, and the page should be fixed. Second, the new database that
is waiting for setVersion to proceed will get an onblocked event, so
the page should know that something is wrong.

I really don't think this is that big of a deal, and certainly not
worth changing the opt-in vs. opt-out behavior that we've settled on.

-Ben

Received on Tuesday, 8 February 2011 19:51:53 UTC