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

RE: [indexeddb] IDBDatabase.setVersion non-nullable parameter has a default for null

From: Mark Pilgrim <pilgrim@google.com>
Date: Fri, 10 Jun 2011 19:13:53 -0400
Message-ID: <BANLkTim+1iYsOfbQeAhMZNMg-GTUKz-+fA@mail.gmail.com>
To: Eliot Graff <Eliot.Graff@microsoft.com>
Cc: Jonas Sicking <jonas@sicking.cc>, "public-webapps@w3.org" <public-webapps@w3.org>, Jeremy Orlow <jorlow@chromium.org>, Israel Hilerio <israelh@microsoft.com>
On Jun 10, 2011 6:56 PM, "Eliot Graff" <Eliot.Graff@microsoft.com> wrote:
>
> ...
> > > Are we saying that we should remove the "TreatNullAs=EmptyString" and
> > keep the parameter restriction that "version" cannot be nullable?
> >
> > I think we should remove any extended attributes from the IDL and just
use
> > the default behavior. It is much less important to me what the actual
default
> > behavior is, than that we use the default behavior which presumably is
the
> > most common behavior.
> >
> > So, "yes" :)
> >
> > / Jonas
> >
>
> I removed [TreatNullAs=EmptyString] from IDBDatabase.setVersion() and
IDBDatabaseSync.setVersion.

Wait, does this mean that setVersion(null) is the same as
setVersion("null")?
Received on Friday, 10 June 2011 23:14:19 GMT

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