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

Re: Maybe we should think about Interface.isInterface functions again

From: Allen Wirfs-Brock <allen@wirfs-brock.com>
Date: Wed, 7 Aug 2013 11:33:30 -0700
Cc: Travis Leithead <travis.leithead@microsoft.com>, Boris Zbarsky <bzbarsky@MIT.EDU>, "public-script-coord@w3.org" <public-script-coord@w3.org>
Message-Id: <566E2D76-BB1E-4D11-8DF6-A2CEFC452BD0@wirfs-brock.com>
To: Domenic Denicola <domenic@domenicdenicola.com>

On Aug 7, 2013, at 10:21 AM, Domenic Denicola wrote:

> Thanks Travis, for some reason I seem to have confused myself about `Element.prototype instanceof Element` over the course of this thread.
> The duck-typing approach seems neat, but note that `Element.prototype` has a `querySelector` method that just throws, saying things like "TypeError: value does not implement interface Element."

So?  Why would anybody intentionally place Element.prototype into an Elements collection?  It's surely a bug if they do so and in that case 'findAll' will detect the bug when it tries to call the method.  Case already handled!


Received on Wednesday, 7 August 2013 18:34:05 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:17 UTC