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

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

From: liorean <liorean@gmail.com>
Date: Wed, 19 Mar 2008 15:24:16 +0100
Message-ID: <cee13aa30803190724w206250l146831a7ae018ce8@mail.gmail.com>
To: "Web APIs WG (public)" <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...

On 19/03/2008, Lachlan Hunt <lachlan.hunt@lachy.id.au> wrote:
> 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.

Why not Entity and EntityReference as well? Both types can parent
nodes in a similar way to DocumentFragment.
-- 
David "liorean" Andersson
Received on Wednesday, 19 March 2008 14:25:09 GMT

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