Re: [selectors-api] Why have two identical differently named interfaces? from Boris Zbarsky on 2008-03-12 (public-webapi@w3.org from March 2008)

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Wed, 12 Mar 2008 10:27:50 -0500
To: Anne van Kesteren <annevk@opera.com>
CC: Web APIs WG <public-webapi@w3.org>
Message-ID: <47D7F676.1030900@mit.edu>

Anne van Kesteren wrote:
> The reason for two interfaces is to allow extensions to either going 
> forward. Though presumably for ECMAScript you can implement them however 
> you'd like as window.ElementSelector and window.DocumentSelector should 
> probably not exist. (Just prototype Element/Document instead.)

Making them not exist is quite a bit of pain in Gecko, for what it's worth.

I guess I could do the two interfaces, but I'm having a hard time seeing 
different extensions being made to these two interfaces (as opposed to wholly 
new interfaces being invented, as was done here).

-Boris

Received on Wednesday, 12 March 2008 15:28:39 UTC