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

RE: [indexeddb] Using WebIDL Dictionary in IDBObjectStore.createIndex for optionalParameters

From: Israel Hilerio <israelh@microsoft.com>
Date: Tue, 7 Jun 2011 18:26:29 +0000
To: Cameron McCormack <cam@mcc.id.au>, Jonas Sicking <jonas@sicking.cc>
CC: "public-webapps@w3.org" <public-webapps@w3.org>
Message-ID: <F695AF7AA77CC745A271AD0F61BBC61E3D146BDB@TK5EX14MBXC115.redmond.corp.microsoft.com>
On Monday, June 06, 2011 3:25 PM, Cameron McCormack wrote:
> Jonas Sicking:
> > I don't know about other APIs. But it does seem very unfortunate to
> > simply silently ignore unknown arguments to
> > IDBDatabase.createObjectStore. Though then again, extra (and thus
> > unknown) arguments are ignored to all other DOM calls.
> Right (not as defined in Web IDL at the moment, but will be soon).
> --
> Cameron McCormack ≝ http://mcc.id.au/

Jonas, could you elaborate why it is so important to reject/throw on the existence of any other properties on the optional parameters?  What are the side effects you believe we need to contain? 

Based on this thread, it seems like this behavior is inconsistent with what JS developers expect and how DOM APIs are designed.

From our point of view, we don't believe getters and setters should be artificially restricted and we agree with Cameron on allowing our methods to take extra parameters and ignore them.

Received on Tuesday, 7 June 2011 18:27:06 UTC

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