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

[Bug 11375] New: [IndexedDB] Error codes need to be assigned new numbers

From: <bugzilla@jessica.w3.org>
Date: Mon, 22 Nov 2010 12:43:09 +0000
To: public-webapps@w3.org
Message-ID: <bug-11375-2927@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11375

           Summary: [IndexedDB] Error codes need to be assigned new
                    numbers
           Product: WebAppsWG
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Indexed Database API
        AssignedTo: dave.null@w3.org
        ReportedBy: jorlow@chromium.org
         QAContact: member-webapi-cvs@w3.org
                CC: mike@w3.org, public-webapps@w3.org


The error codes specced in IDBDatabaseException's interface need to be redone. 
They currently overlap with existing exception error codes and use 0 which
we've avoided using in the past [0].  In addition, the codes are non-contiguous
which also seems to be non-standard.  We should re-map the exception numbers
into something contiguous that doesn't overlap with other exception codes.


[0] I'm not sure if 0 is actually specced to be reserved, but in practice it
seems to be.  And WebKit uses 0 internally to signal "no exception".

-- 
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 Monday, 22 November 2010 12:43:14 GMT

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