9653 2010-05-04 16:56:06 +0000 How to handle nullable violations is not specified. 2011-07-05 17:31:34 +0000 1 1 1 Unclassified WebAppsWG Indexed Database API unspecified All All RESOLVED FIXED P2 normal --- 1 sdwilsh nikunj.mehta eliotgra jonas jorlow mike public-webapps public-webapps-bugzilla oldest_to_newest 35402 0 sdwilsh 2010-05-04 16:56:06 +0000 The spec doesn't say what the correct course of action is if a consumer passes null to something that is not null. 42283 1 jonas 2010-11-08 18:35:51 +0000 Is this still a problem. I've tried to be thorough in defining invalid values everywhere. The sync API is still not up-to-date, but that's a bigger problem that we should handle separately. 43242 2 jorlow 2010-12-10 12:23:06 +0000 Are you planning on working on this soon? If not, maybe you should assign it to dave.null@w3.org 50683 3 eliotgra 2011-07-05 17:31:34 +0000 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