W3C home > Mailing lists > Public > www-style@w3.org > August 2015

Re: [selectors] feedback

From: Anne van Kesteren <annevk@annevk.nl>
Date: Thu, 27 Aug 2015 10:21:39 +0200
Message-ID: <CADnb78how=wRMm27jtOpKLsP8edE9AaaMzuYZP+y62BpeDOYrg@mail.gmail.com>
To: fantasai <fantasai.lists@inkedblade.net>
Cc: "www-style@w3.org" <www-style@w3.org>
On Thu, Aug 27, 2015 at 9:41 AM, fantasai <fantasai.lists@inkedblade.net> wrote:
> Right, this text doesn't appear in the section on :empty.

I don't understand how that makes sense.

> Perhaps you're misunderstanding what I meant. DOM provides the entire
> DOM tree for pattern-matching--of course. But for its .query methods
> the DOM spec compiles the list of elements that are potential output
> and filters them by whether or not they match. Selectors only defines
> what it means for an element to match.

How does that solve anything for pseudo-elements, which are not
elements and cannot be matched?

> This way Selectors doesn't need to decide what elements are valid
> output, or define how to traverse the DOM tree to find said potential
> output elements, or define out the output of .querySelector is sorted
> or otherwise represented. These are particulars of the .query methods,
> not particulars of how selectors work, so they belong in DOM, not in
> Selectors.

Yeah maybe. It's somewhat annoying that we're revisiting this setup a
good year after we decided on something. Feel free to provide PRs
here: https://github.com/whatwg/dom.

Received on Thursday, 27 August 2015 08:22:06 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 27 August 2015 08:22:06 UTC