Repository navigation
Avoid repeated sibling scans when repairing unclosed tags - #323
Merged
Merged
Conversation
Assisted-by: OpenAI Codex
raymondstudio
marked this pull request as ready for review
October 17, 2026 09:07
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.
Repairing an unclosed element with many children moves each child through
appendChild, which repeatedly filters the remaining source siblings. Cleanup becomes quadratic. Detach the child list once, then reuse the existing append operation. The same-tag and different-tag repair destinations, child order, parent pointers andparseNoneClosedTagsbehavior stay intact.This is a synthetic current-9.0.4 reduction related to #260 and #280. It does not establish that the original live-site inputs in those reports are fixed.
Validation on Windows with Node 24.19.0 and Bun 1.3.14:
Validation limits: the exact
CI=true bun run test:cicommand fails during Bun's Windows copy of the local@test/rootdependency, before starting tests. The underlying complete compiled test tree was run directly. Source tests (ts-nodeinitialization,fileExistsundefined) and lint (TypeScript ESLint initialization,version.splitundefined) encounter existing locked-toolchain failures. These checks are not reported as passed; hosted Linux CI and the full Node matrix remain pending. No dependencies, lockfiles, tests or checks were removed or disabled.Prepared and independently reviewed with OpenAI Codex agents. Human maintainer review is pending; this is a draft, with no merge or release requested.