This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The spec doesn't say what the correct course of action is if a consumer passes null to something that is not null.
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.
Are you planning on working on this soon? If not, maybe you should assign it to dave.null@w3.org
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