I just updated the editor's Draft with the information from this thread (the definitions from [1] also making keypath nullable, as Cameron pointed out).
Rewrote 3.1.12, Options Objects, to define the dictionary objects IDBDatabaseOptionalParameters and IDBIndexOptionalParameters (removing the Note, the Issue, and the two sentences about exceptions). Changed types from the optionalParameters type to the new types in IDBObjectStore.createObjectStore (IDBDatabase and IDBDatabaseSync) and in IDBIndex createIndex (IDBObjectStore and IDBObjectStoreSync). Let me know if I missed anything. Thanks, Eliot [1] http://lists.w3.org/Archives/Public/public-webapps/2011AprJun/1073.html > -----Original Message----- > From: public-webapps-requ...@w3.org [mailto:public-webapps- > requ...@w3.org] On Behalf Of Israel Hilerio > Sent: Thursday, June 16, 2011 5:16 PM > To: Cameron McCormack > Cc: Jonas Sicking; timeless; public-webapps@w3.org > Subject: RE: [indexeddb] Using WebIDL Dictionary in > IDBObjectStore.createIndex for optionalParameters > > On Thursday, June 16, 2011 3:09 PM, Cameron McCormack wrote: > > Israel Hilerio: > > > Great! I will work with Eliot to update the spec for the two APIs > > > below, including their Synchronous counterparts, with: > > > ------- > > > dictionary IDBDatabaseOptionalParameters { > > > DOMString keyPath = null; > > > > That would need to be > > > > DOMString? keyPath = null; > > > > (or else just write “DOMString keyPath;” and state in prose what it > > means if the dictionary member was not specified). > > > > -- > > Cameron McCormack ≝ http://mcc.id.au/ > > Good catch! I will make sure add: > DOMString? keyPath = null; > > Israel
