Add PARSER_MEDIA_TYPE option to support strict XHTML documents#568
Merged
cure53 merged 1 commit intocure53:mainfrom Sep 14, 2021
Merged
Add PARSER_MEDIA_TYPE option to support strict XHTML documents#568cure53 merged 1 commit intocure53:mainfrom
cure53 merged 1 commit intocure53:mainfrom
Conversation
Owner
|
This looks great, thank you very much! Running tests now... |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Background & Context
DOMPurify assumes input is HTML and forces text/html media type when the input is parsed with DOMParser. We would like to have the ability to parse the input as XHTML with media type application/xhtml+xml. This will make DOMParser even more strict and for example allow only lowercase tag and attribute names.
Tasks