- From: Pedram Emrouznejad <notifications@github.com>
- Date: Tue, 03 Oct 2017 13:23:48 +0000 (UTC)
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 3 October 2017 13:24:12 UTC
> Well, there is a subtle semantics difference. We’re essentially checking whether :matches(selector) is true or not for each element, and collecting elements that do match so we’re not scope-matching a selectors string but instead we’re matching a selector against an element which uses a different scoping object. This is because using a node from different trees as the scope doesn’t make sense in evaluating a selector as well as for the implementation simplicity. > > We’re adopting this API in some Safari code for now, and if this turns out to be useful, we’d make a more refined proposal. @rniwa do you have any updates of how this is going in Safari? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/webcomponents/issues/78#issuecomment-333840160
Received on Tuesday, 3 October 2017 13:24:12 UTC