- From: Jonas Sicking <jonas@sicking.cc>
- Date: Fri, 9 Sep 2011 10:11:54 -0700
- To: Cameron McCormack <cam@mcc.id.au>
- Cc: public-script-coord@w3.org
On Fri, Sep 9, 2011 at 1:50 AM, Cameron McCormack <cam@mcc.id.au> wrote: > On 26/08/11 6:21 AM, Jonas Sicking wrote: >> >> The 'caller' annotation in WebIDL makes an object callable. This is >> needed for legacy support at least for the document.all (non-firefox >> browsers also support it on other objects, but it's not been >> established that this is actually needed for webcompat). >> >> My understanding is that this convention is not implementable in >> Javascript. >> >> I think we should remove this from WebIDL as to prevent the pattern >> from spreading any further. Apparently the DAP contacts API has >> started using it, as has the microdata DOM API. So it appears that >> putting it in WebIDL has made it easier for the pattern to spread. >> >> Prose can always be added to the document.all object (and other >> objects too if needed) as to make them callable. > > I'd like to wait to see what the results of the WebKit experiments are, and > whether that indicates whether the non-HTMLAllCollection callers will be > removed from the HTML spec. > > For the moment, I will give Anne's suggestion a try -- I'll leave it in the > spec, and rename it to legacycaller. > > http://dev.w3.org/cvsweb/2006/webapi/WebIDL/Overview.html.diff?r1=1.394;r2=1.395;f=h > > Jonas, can you indicate whether this resolution is satisfactory? I'm ok with this for now, but I don't want to leave things in this state forever without getting feedback from webkit that legacycaller is really needed in as many interfaces as it's currently used. / Jonas
Received on Friday, 9 September 2011 17:13:01 UTC