You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
and the strict mode is off, then the parser ends up calling ontext event with the value of content&x</a>\n .
Root cause
This is caused by the assumption that when an illegal entity character is parsed it should remain part of the text for the tag, which occurs at lib/sax.js line 1492.
Solution outline
To fix this would probably require changing the code around line 1492 to something like the following
i--// reprocess the illegal characterparser[buffer]+='&'+parser.entityparser.entity=''parser.state=returnState
The text was updated successfully, but these errors were encountered:
Problem
When an xml file has data that looks like
and the strict mode is off, then the parser ends up calling ontext event with the value of
content&x</a>\n
.Root cause
This is caused by the assumption that when an illegal entity character is parsed it should remain part of the text for the tag, which occurs at lib/sax.js line 1492.
Solution outline
To fix this would probably require changing the code around line 1492 to something like the following
The text was updated successfully, but these errors were encountered: