Repository navigation
Conversation
commit: |
cowboyd
marked this pull request as ready for review
November 16, 2026 04:12
cowboyd
force-pushed
the
dom-query-selectors
branch
from
November 16, 2026 13:42
878d01e to
499a2cc
Compare
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
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.
What does this PR do?
Adds initial
querySelector()andquerySelectorAll()support to Document and Element, using the css-select adapter introduced in #80. This is the next selector-support step, stacked on that PR.Document queries include the document element; Element queries search descendants.
querySelector()returns the first match ornull.querySelectorAll()returns a static, element-onlyNodeListwith indexed access,item(), and iteration methods delegated to its backing array.Type of change
Checklist
AI-generated code disclosure