W3C home > Mailing lists > Public > public-webapi@w3.org > May 2008

Re: [selectors-api] Why have two identical differently named interfaces?

From: Lachlan Hunt <lachlan.hunt@lachy.id.au>
Date: Fri, 02 May 2008 15:51:45 +0200
Message-ID: <481B1C71.8060906@lachy.id.au>
To: Boris Zbarsky <bzbarsky@MIT.EDU>
Cc: Web APIs WG <public-webapi@w3.org>

Boris Zbarsky wrote:
> Is there a reason to have identical interfaces called DocumentSelector 
> and ElementSelector that are identical?  Would it not make sense to just 
> define a NodeSelector or something and require Document and Element 
> nodes to implement it?  The confromance requirement could be easily 
> stated in terms of descendants of the Node in question in a way that 
> would work for both Document and Element nodes...

I have updated the editor's draft to define a single NodeSelector 
interface that is implemented by Document and Element nodes.

You can review the changes in the latest editor's draft.


Please let me know whether or not you are satisfied.

Lachlan Hunt - Opera Software
Received on Friday, 2 May 2008 13:52:24 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:16:26 UTC