W3C home > Mailing lists > Public > public-script-coord@w3.org > July to September 2011

Re: Removing 'caller' from WebIDL

From: Brendan Eich <brendan@mozilla.org>
Date: Wed, 31 Aug 2011 23:11:09 -0700
Cc: Anne van Kesteren <annevk@opera.com>, public-script-coord@w3.org, Boris Zbarsky <bzbarsky@mit.edu>, Ian Hickson <ian@hixie.ch>
Message-Id: <1EE32318-5A22-487E-A450-ADA00CDBBBBD@mozilla.org>
To: Cameron McCormack <cam@mcc.id.au>
On Aug 31, 2011, at 10:05 PM, Cameron McCormack wrote:

> The other collections in the HTML spec still do require callers (HTMLFormControlsCollection, HTMLOptionsCollection, HTMLPropertiesCollection and HTMLFormElement).
> I did raise http://www.w3.org/Bugs/Public/show_bug.cgi?id=11032 at some point about removing callers from HTMLPropertiesCollection but that ended up WONTFIX.
> Ian, are you sure we need callers on anything more than document.all?

There's no "need", Hixie simply decided "for consistency with the other collections.

But Gecko has not made any other collections callable than document.all, and we don't plan ever to do any such thing. There's no interop requirement, and caller is not supportable in JS (important when proxy-wrapping and self-hosting, e.g. dom.js).

Ecma TC39ers two years ago made a clear plea to avoid propagating caller beyond what legacy web compatibility seem sto require, which is only document.all in our (Mozilla's) experience.

What can be done to remove the caller uses other than document.all from HTML's spec?

Received on Thursday, 1 September 2011 06:11:53 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:37:45 UTC