[selectors-api] Why have two identical differently named interfaces? from Boris Zbarsky on 2008-03-12 (public-webapi@w3.org from March 2008)

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Tue, 11 Mar 2008 22:08:30 -0500
To: Web APIs WG <public-webapi@w3.org>
Message-ID: <47D7492E.7060603@mit.edu>

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...

-Boris

Received on Wednesday, 12 March 2008 03:08:56 UTC