- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Fri, 28 Mar 2014 18:37:58 -0700
- To: Anne van Kesteren <annevk@annevk.nl>
- Cc: "www-style@w3.org" <www-style@w3.org>, Domenic Denicola <domenic@domenicdenicola.com>
On Fri, Mar 21, 2014 at 9:24 AM, Anne van Kesteren <annevk@annevk.nl> wrote: > In the context of CSS there's numerous places where you'd want to > parse a selector, or match a parsed selector against a tree. I don't > see why APIs, such as querySelector(), need a special entry point. > Contrast with HTML parsing, which is defined in a single place and > numerous APIs reference that directly, perhaps with slightly different > inputs as to what the encoding should be and whether or not scripting > is enabled. You're right. I've removed the "match a selector" section, and instead just beefed up the "evaluate a selector" section to be appropriate as an API hook. Please update your references accordingly. ~TJ
Received on Saturday, 29 March 2014 01:38:46 UTC