- From: Rich Tibbett <richt@opera.com>
- Date: Thu, 25 Aug 2011 10:54:56 +0200
- To: Andreas Gal <gal@mozilla.com>
- CC: public-device-apis@w3.org
Andreas Gal wrote:
>
> 4.2 Contacts interface
>
> [NoInterfaceObject]
> interface Contacts {
> caller void find
> <http://www.w3.org/TR/contacts-api/#widl-Contacts-find-caller-void-DOMStringArray-fields-ContactFindCB-successCB-ContactErrorCB-errorCB-ContactFindOptions-options>
> (DOMString[] fields, |ContactFindCB|
> <http://www.w3.org/TR/contacts-api/#idl-def-ContactFindCB> successCB,
> optional |ContactErrorCB|
> <http://www.w3.org/TR/contacts-api/#idl-def-ContactErrorCB> errorCB,
> optional |ContactFindOptions|
> <http://www.w3.org/TR/contacts-api/#idl-def-ContactFindOptions> options);
> };
>
> To quote from WebIDL,
> http://dev.w3.org/2006/webapi/WebIDL/Overview.html#idl-callers
>
> Specifications SHOULD NOT use callers unless required to specify the
> behavior of legacy APIs. (emphasis theirs, not mine)
>
> Callable objects step outside the semantics of ECMAScript and can't be
> self-hosted.
>
> I would much prefer if we drop the caller annotation here. Any objections?
>
This was already fixed in the editor's draft based on previous feedback [1]:
http://dev.w3.org/2009/dap/contacts/
- Rich
[1]
http://dev.w3.org/cvsweb/2009/dap/contacts/Overview.html.diff?r1=1.148;r2=1.149;f=h
Received on Thursday, 25 August 2011 08:55:37 UTC