W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2010

[Bug 11097] New: [IndexedDB] Behavior of .close() is not completely specified

From: <bugzilla@jessica.w3.org>
Date: Tue, 19 Oct 2010 17:36:24 +0000
To: public-webapps@w3.org
Message-ID: <bug-11097-2927@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11097

           Summary: [IndexedDB] Behavior of .close() is not completely
                    specified
           Product: WebAppsWG
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Indexed Database API
        AssignedTo: andreip@google.com
        ReportedBy: jorlow@chromium.org
         QAContact: member-webapi-cvs@w3.org
                CC: mike@w3.org, public-webapps@w3.org


The spec defines what should happen if .transaction() is called after .close(),
but it doesn't specify the rest. For example, what happens if I call
database.objectStores or .version. Or I touch my IDBIndex object. Or so on. It
seems like most if not all of this should return exceptions.

It's also kind of odd that we have different behavior specified for when
.close() is called and when we actually finish the close. Maybe we should
return an IDBRequest object and fire an onsuccess when the close is complete?

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Tuesday, 19 October 2010 17:36:31 GMT

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