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

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

From: Lachlan Hunt <lachlan.hunt@lachy.id.au>
Date: Wed, 19 Mar 2008 14:14:09 +0100
Message-ID: <47E111A1.90201@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 made this change as suggested, and defined that it is to be 
implemented by all objects that implement either the Document, Element 
or DocumentFragment interfaces.

This change will be reflected in the next editor's draft.

-- 
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
Received on Wednesday, 19 March 2008 13:14:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 19 March 2008 13:14:46 GMT