Re: [whatwg/dom] Match querySelector for pseudo elements (::slotted()) (#463)

> That said, if we really do think it's a necessity to impose a "must stay in starting tree" restriction, I won't oppose it if we couple it with an issue tracking adding a flag or new method that actually evaluates selectors properly, the same as the browser does. Before we impose this restriction in the spec I'd like to figure out what the new API will look like; I dont' want a querySelector2(...) sort of thing, or some huge unwieldy name that people won't want to type.

Let me make sure one thing.

Putting aside pseudos, if I understand the whatwg DOM spec,
https://dom.spec.whatwg.org/#dom-parentnode-queryselector
https://dom.spec.whatwg.org/#scope-match-a-selectors-string
> 3. Return the result of evaluate a selector s against node’s root using scoping root node.

not returning elements outside the tree of the context object is status quo, right?

Or, according to changes in
https://drafts.csswg.org/selectors-4/#changes
under section 18 API Hooks,

> Note that earlier versions of this section defined a section on **evaluating a selector**, but that section is no longer present. Specifications referencing that section should instead reference the algorithm to **match a selector against a tree**.

Is this change not applied to the DOM spec (but how we pass *one or more root elements* from querySelector()?)?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/463#issuecomment-325574143