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

Re: [IndexedDB] Spec Question on IDBFactory open method

From: Jonas Sicking <jonas@sicking.cc>
Date: Thu, 21 Apr 2011 16:16:07 -0700
Message-ID: <BANLkTi=ouK3nuUNe52Gq1LUFttNZ35nwWg@mail.gmail.com>
To: Israel Hilerio <israelh@microsoft.com>
Cc: "sdwilsh@mozilla.com" <sdwilsh@mozilla.com>, "public-webapps@w3.org" <public-webapps@w3.org>
On Thu, Apr 21, 2011 at 11:16 AM, Israel Hilerio <israelh@microsoft.com> wrote:
> On Wed, Apr 20, 2011 at 3:16 PM, Jonas Sicking wrote:
>>On Wed, Apr 20, 2011 at 1:46 PM, Shawn Wilsher wrote:
>> > On Wed, Apr 20, 2011 at 1:33 PM, Israel Hilerio <israelh@microsoft.com> wrote:
>> > > The open method description in the IDBFactory talks about setting the
>> > >source of the IDBRequest to "no source".  What does "no source" means
>> > >("undefined", "null", other)?
>> > >
>> > > In addition, what should be the value of the transaction property in the
>> > > IDBRequest object returned from the open method?  It seems this should be
>> > > either "undefined" or null.
>> >
>> > I think undefined makes sense for both of these.
>> >
>> > Cheers,
>> >
>> > Shawn
>>
>> It's (almost) just an internal property, so it doesn't really matter.
>> There is no way to check.
>>
>> However we should make sure that IDBRequest.source returns null when
>> the source is set to "no source".
>>
>> / Jonas
>
> We see that it can go either way.  However, we believe it should be null.  Recently, we've been using undefined to signal properties that are not available to developers and null to signal unassigned values.  If we agree, I can open a bug on this. Let me know.

Yeah, I think 'null' is the right thing to return from .source

/ Jonas
Received on Thursday, 21 April 2011 23:17:04 GMT

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