W3C home > Mailing lists > Public > public-html@w3.org > October 2010

Re: getting rid of callers

From: Adam Barth <w3c@adambarth.com>
Date: Tue, 12 Oct 2010 23:21:38 -0700
Message-ID: <AANLkTinjBRL=_fSBaqETENJ-fWAgAQiWE7MMD2vCeab7@mail.gmail.com>
To: Maciej Stachowiak <mjs@apple.com>
Cc: Cameron McCormack <cam@mcc.id.au>, public-html@w3.org
On Tue, Oct 12, 2010 at 10:47 PM, Maciej Stachowiak <mjs@apple.com> wrote:
> On Oct 12, 2010, at 9:14 PM, Cameron McCormack wrote:
>> Various HTML*Collection interfaces and the HTMLFormElement interface
>> define callers.  Callers seem unpopular with many people, so I am
>> wondering how many can actually be safely removed from the spec.
>>
>> Here are some tests I ran to see where they’re implemented:
>>
>>  http://people.mozilla.com/~cmccormack/tests/callers.html
>>  http://people.mozilla.com/~cmccormack/tests/callers-quirks.html
>>
>> The results are here:
>>
>>  http://people.mozilla.com/~cmccormack/tests/callers-results.html
>>
>> (I left out the HTMLPropertyCollection ones since nobody implements that
>> yet.)
>>
>> So of all the callers, Firefox has been getting away with only
>> implementing document.all("blah"), and only for quirks mode.
>>
>> For HTMLFormElement, it seems only IE implements them.  Are they really
>> necessary to have in the spec?
>>
>> I don’t have any data on any of this.  Does anyone else?  Any browser
>> vendors willing to drop any of these callers? :)
>
> From your results, it seems like Firefox is the odd man out. I think the case against would have to be pretty compelling for every other browser to change to match Firefox.
>
> I realize some people find custom call behavior distasteful, but it's not really clear to me what the practical problem is with it.
>
> Also, I find quirks-mode-only DOM behaviors more distasteful than custom call behavior, so if document.all needs it at all, I'd rather do it everywhere than limit to quirks mode.
>
> I do agree that it would be better not to propagate custom call behavior to objects that didn't have it before. I don't think there is much need for HTMLPropertyCollection to be an HTMLCollection.

Here's a related WebKit bug that's received some recent discussion:

https://bugs.webkit.org/show_bug.cgi?id=14547

The question there is what typeof should return for these callable
objects (i.e., "object" or "function").

Adam
Received on Wednesday, 13 October 2010 06:22:46 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:20 UTC