Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

#908@minor: Adds support for endoing HTML entities to the XML parser.… #912

Conversation

capricorn86
Copy link
Owner

… Adds support for escaping text to XMLSerializer.serializeToString().

… Adds support for escaping text to XMLSerializer.serializeToString().
@capricorn86 capricorn86 linked an issue May 11, 2023 that may be closed by this pull request
@capricorn86 capricorn86 self-assigned this May 11, 2023
…o task/908-domparserparsefromstring-doesnt-decode-html-entities
@capricorn86 capricorn86 merged commit a895911 into master May 11, 2023
1 check passed
@capricorn86 capricorn86 deleted the task/908-domparserparsefromstring-doesnt-decode-html-entities branch May 11, 2023 23:03
@adaboese
Copy link

How to opt-out from decoding of HTML entities?

@btea
Copy link
Contributor

btea commented Dec 26, 2023

@adaboese You can only use lower versions that have not yet been implemented or modify the source code.
I'd like to ask, why do you want to do this? 🤔

@adaboese
Copy link

The current implementation breaks HTML.

<li>%3Chtml%3E</li>

becomes

<li><html></li>

@btea
Copy link
Contributor

btea commented Dec 29, 2023

It seems to be a problem with entities.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

DOMParser().parseFromString(...) doesn't decode html entities
3 participants