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

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

From: Jonas Sicking <jonas@sicking.cc>
Date: Wed, 19 Mar 2008 09:15:20 -0700
Message-ID: <47E13C18.2040909@sicking.cc>
To: liorean <liorean@gmail.com>
CC: "Web APIs WG (public)" <public-webapi@w3.org>

liorean wrote:
>>  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.

Given the very poor support for those node types in current UAs (does 
anyone support them at all?) I would rather not add more functionality 
to them.

/ Jonas
Received on Wednesday, 19 March 2008 16:16:39 UTC

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