Decode attribute content differently from text node content #255
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.
As described in issue #254
¶
is a full complete characterreference when decoding text node content, but not when
decoding attribute content which causes problems for URL attribute
values like
As shown via JS test code in that issue, a small set of
next characters prevent a character reference name match
from being considered complete.
This commit:
boolean inAttribute
, and modifies the Trie traversalloops to not store a longest match so far based on that
parameter and some next character tests
@deprecated
This change should make us more conformant with observed
browser behaviour so is not expected to cause compatibility
problems for existing users.
Fixes #254