Add regression tests for XML parser idempotency issues#6747
Closed
Add regression tests for XML parser idempotency issues#6747
Conversation
Adds tests covering XML parser failure patterns reported in moderneinc/customer-requests#857: - Comment in prolog followed by blank lines then root element - xmldecl followed by comment then blank lines then root element - xmldecl with standalone="no" attribute - Comment with triple-dash inside element content - xmldecl after comment correctly produces ParseError (malformed XML) - xmldecl followed by comment then root element - WSDL-style xmldecl with standalone="no" All idempotency patterns pass on the current parser, confirming that the cursor refactoring and JSP parser support added in 2025 resolved the previously reported failures.
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
1 participant
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.
Summary
Analysis of the raw data revealed:
<?xml?>after comments (25 AEM.content.xmlfiles) — correctly producesParseErrorfor malformed XMLAll tests pass on the current parser, confirming these issues are resolved. Tests cover:
standalone="no"ParseError