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

# liorean (18 years ago)

On 12/03/2008, Boris Zbarsky <bzbarsky at mit.edu> wrote:

I guess I could do the two interfaces, but I'm having a hard time seeing different extensions being made to these two interfaces (as opposed to wholly new interfaces being invented, as was done here).

I can actually imagine one extension that only makes sence on elements and not on any other nodes - element-rooted instead of subtree-only-but-document-rooted queries. (I don't see any real benefit from such an interface though, but I've seen the idea mentioned on the mailing lists.)

# liorean (18 years ago)

Oops, don't know how I ended up sending that to this mailing list - it was intended for the WebAPI WG list...