Top level > in query about cascadia

[andybalholm]

I don't think there is any way to do that in Cascadia without changing the API. Potentially there could be a CompileWithContext function, and you could pass it the current node along with the selector. But I think it would make more sense to handle this at the goquery level, where the selectors are being passed as strings.

[anacrolix]

That seems unfortunate. I think implementing this in cascadia level would be more performant and natural.

[andybalholm]

Actually, implementing it in goquery would have better performance, since it would not need to scan all the descendant nodes and check each one to see if it is an immediate child. It could just iterate over the child nodes and return the ones that match the remainder of the selector.

But I just realized that would only work if the remainder of the selector is all in reference to one node. If it's referring to descendants of that child node, things get really complicated.

[andybalholm]

I'm closing all requests for context-sensitive selectors as wontfix.