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 <[EMAIL PROTECTED]> 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
