- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Fri, 21 Mar 2014 16:24:29 +0000
- To: "Tab Atkins Jr." <jackalmage@gmail.com>
- Cc: "www-style@w3.org" <www-style@w3.org>, Domenic Denicola <domenic@domenicdenicola.com>
On Thu, Mar 20, 2014 at 6:13 PM, Tab Atkins Jr. <jackalmage@gmail.com> wrote: > On Thu, Mar 20, 2014 at 3:58 AM, Anne van Kesteren <annevk@annevk.nl> wrote: >> On Wed, Mar 19, 2014 at 7:02 PM, Tab Atkins Jr. <jackalmage@gmail.com> wrote: >> [...] > > I thought querySelector() took additional arguments for setting the > context object? query()/queryAll() did in the Selectors API Level 2 draft, but Domenic and I could not figure out how that would be different from using the methods on either the node in question or on an Elements instance. >> * I don't understand why there is a specific API-entry point for >> matching selectors against a tree. It seems that should just be one >> algorithm. > > I don't understand what you mean. 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. -- http://annevankesteren.nl/
Received on Friday, 21 March 2014 16:24:56 UTC