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

[Bug 9653] How to handle nullable violations is not specified.

From: <bugzilla@jessica.w3.org>
Date: Tue, 05 Jul 2011 17:31:35 +0000
To: public-webapps@w3.org
Message-Id: <E1Qe9TD-0005ti-Kc@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9653

Eliot Graff <eliotgra@microsoft.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |eliotgra@microsoft.com
         Resolution|                            |FIXED

--- Comment #3 from Eliot Graff <eliotgra@microsoft.com> 2011-07-05 17:31:34 UTC ---
>From mail [1]:

]]
Based on this conversation, we agreed that we wanted to throw a TypeError when
a non-nullable parameter was passed a null argument.  This implies to me, for
example, that if we were to pass a null value for the key parameter of
IDBObjectStore.put we will throw a TypeError (i.e. InvalidArgument).  We're
assuming this Exception takes precedence over any IDB Exceptions (i.e.
DATA_ERR).
[[

I believe that this satisfies the request in this bug, so I am resolving it as
fixed.

[1] http://lists.w3.org/Archives/Public/public-webapps/2011AprJun/0917.html

-- 
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, 5 July 2011 17:31:36 GMT

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