W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2011

[Indexeddb} Bug # 9653 - nullable violations on parameters

From: Israel Hilerio <israelh@microsoft.com>
Date: Wed, 27 Apr 2011 01:57:03 +0000
To: "public-webapps@w3.org" <public-webapps@w3.org>
CC: Victor Ngo <vicngo@microsoft.com>
Message-ID: <F695AF7AA77CC745A271AD0F61BBC61E3D02E0B2@TK5EX14MBXC113.redmond.corp.microsoft.com>
Did you come up with a conclusion on how to handle null violations:
* Bug 9653 [1] - How to handle nullable violations is not specified.
I looked for previous threads and couldn't find anything.

It seems to me we should throw a NON_TRANSIENT_ERR when a developer uses a null value on a non-nullable parameter.  What do you think?


[1] http://www.w3.org/Bugs/Public/show_bug.cgi?id=9653
Received on Wednesday, 27 April 2011 01:57:32 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:19 UTC