Fix incorrect serialization of special characters in raw text elements #1566
+26
−4
Conversation
This file contains 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
|
Some tests are failing, but they seem to be entirely unrelated to the changes in this PR? The tests ran successfully on my machine. |
capricorn86
approved these changes
Nov 6, 2024
There was a problem hiding this comment.
Thank you for your contribution @BenjaminAster! ⭐
Sorry that it took such a long time to get this in.
There are some flaky tests that are based on timers. I'm trying to create a list of them and will hopefully fix it soon. |
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.
When raw text elements (e.g.
<script>,<style>) get serialized in Happy-DOM, the four special characters&,<,>and U+00A0 NO-BREAK SPACE incorrectly get escaped as&,<,>and . This PR fixes this behavior to match the specification.