Fix handling of backslashes and Unicode escape sequences in CSS content #398
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.
This PR addresses an issue in the handling of backslashes and Unicode escape sequences in CSS content. The current implementation may incorrectly escape backslashes, which can break valid CSS syntax, especially when dealing with Unicode escape sequences like \00a0.
Changes:
Improved Handling of Backslashes:
The code now correctly distinguishes between backslashes used for escaping specific characters (like " or ) and those that are part of Unicode escape sequences.
If a backslash is followed by a valid Unicode escape sequence (e.g., \00a0), it is preserved as-is.
If a backslash is followed by any other character, it is properly escaped to \.
Added Validation for Unicode Escape Sequences:
A helper function is_valid_unicode_escape is introduced to check if a sequence of characters following a backslash forms a valid Unicode escape sequence.
This ensures that only valid sequences are preserved, while invalid sequences are treated as regular text.
Code Changes: