(Preview) Selectors can match against Nodes #2324
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Extends the QueryParser and Evaluators to support matching nodes (including specific node types, and their nodeValue contents) Allows finding e.g. Elements following a particular comment or text node.
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
First draft of the ability to select nodes, into Nodes<T extends Node>.
... and remove unused root param
|
Does the Nodes class have a DOM update feature like the Elements class? |
Moved applicable bulk methods of Elements into Nodes
@821938089 yup, same as Elements. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This extends the QueryParser and Evaluators to support matching nodes (including specific node types, and their nodeValue contents)
Allows finding e.g. Elements following a particular comment or text node.
E.g.:
::comment:contains(prices) + pwill findpElements directly after a<!-- prices: -->comment.Or:
div:has(>::comment)will finddivElements that directly have comment children.Available operators so far:
::node(matches any leaf node)::text(matches a text node)::comment(matches a comment node)::data(matches a data node):contains(text)when in a node context will match the text against the normalized node valueThis is the first pass; next pass will be to implement various
NodeList selectNodes(css)methods to allow nodes to be selected directly (not just Elements).