- From: Jonas Sicking <jonas@sicking.cc>
- Date: Tue, 7 Jun 2011 01:12:39 -0700
- To: Jeremy Orlow <jorlow@chromium.org>
- Cc: Israel Hilerio <israelh@microsoft.com>, "public-webapps@w3.org" <public-webapps@w3.org>
Actually, WebIDL just changed from turning null into "null" to turning null into "". Turns out that a bunch of functions depended on that behavior and so it seems like that's what we'll be stuck with. In any case, I think IndexedDB should be silent on the issue and simply rely on WebIDL defaults. That should give the most consistent behavior to most other DOM functions. / Jonas On Mon, Jun 6, 2011 at 11:54 PM, Jeremy Orlow <jorlow@chromium.org> wrote: > We should probably just remove the special case. I believe WebIDL specifies > that a null would then turn into the string "null". This is what we've done > pretty much everywhere else I believe. > J > > On Mon, Jun 6, 2011 at 7:23 PM, Israel Hilerio <israelh@microsoft.com> > wrote: >> >> The parameter of IDBDatabase.setVersion is defined in the WebIDL as >> [TreatNullAs=EmptyString] but in the method definition it says that the >> parameter cannot be nullable. Do we want to enable null values? >> >> Israel >> > >
Received on Tuesday, 7 June 2011 08:13:36 UTC