Repository navigation
fix: validator; reject an XML declaration inside an element - #889
Open
Shaisolaris wants to merge 1 commit into
Open
Shaisolaris wants to merge 1 commit into
Shaisolaris wants to merge 1 commit into
Conversation
This branch has not been deployed
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.
Purpose / Goal
XMLValidator.validatereports "XML declaration allowed only at the start of the document." for a declaration before the root, but accepts one inside an element:Input:
Expected:
InvalidXmlerror, "XML declaration allowed only at the start of the document."Actual:
truefor both. libxml2 rejects both documents.Cause: inside tag content the validator calls
readPI(xmlData, ++i), which passes the index of the?instead of the index after<?.readPIthen reads the target as?xml, so thetagname === 'xml'check never matches. The top-level call already passes the position after<?; this change does the same in tag content.Type
Testing:
spec/validator_spec.jsfails before the change and passes after.npx jasmine "spec/*spec.js": 333 specs, 0 failures, 2 pending.benchmark/exercise the parser and builder, not the validator, so I did not include perf numbers. The change only alters an index argument.lib/and the changelog are left for the maintainers, per CONTRIBUTING.