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 17:15:08 +0200
Message-ID: <481B2FFC.4000201@lachy.id.au>
To: Jonas Sicking <jonas@sicking.cc>
Cc: liorean <liorean@gmail.com>, "Web APIs WG (public)" <public-webapi@w3.org>

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

I concur with Jonas.  I have not added support for the NodeSelector 
interface to Entity and EntityReference objects.

Please let me know whether or not you are satisfied with this response.

-- 
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
Received on Friday, 2 May 2008 15:15:50 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 2 May 2008 15:15:50 GMT