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

Re: [selectors] feedback

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Thu, 27 Aug 2015 11:36:00 +0200
Message-ID: <CAAWBYDCUj7RCBiZ+=t_ozcCGmAwJSr04PfTiOtYVdEPdWsSMxw@mail.gmail.com>
To: fantasai <fantasai.lists@inkedblade.net>
Cc: www-style list <www-style@w3.org>
On Thu, Aug 27, 2015 at 9:40 AM, fantasai <fantasai.lists@inkedblade.net> wrote:
> 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.
> 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.

No.  This is *not* okay.  I explained this in an email a few days ago
Writing Selectors solely as a matching predicate is *immensely
inconvenient* for specs trying to actually *use* selectors.

We argued about this last night and it sounded like you agreed with
me.  It's somewhat annoying that an hour later you wrote an email
disagreeing with the conclusion. >_<

Received on Thursday, 27 August 2015 09:36:47 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 27 August 2015 09:36:48 UTC