Repository navigation
Conversation
0.1.2 fixes XML entity and namespace-prefix lookups that resolved Object.prototype names (e.g. &constructor;) instead of failing like jsdom. test:purify-edge passes.
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
1 participant
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.
Bumps the
purify-edgedevDependency used bynpm run test:purify-edgefrom 0.1.1 to 0.1.2.0.1.2 fixes XML parsing in the purify-edge window: entity and namespace-prefix names that collide with
Object.prototypemembers (for example&constructor;or an undeclaredtoString:prefix) resolved instead of failing like jsdom. It was reported in kkomelin/isomorphic-dompurify#498.Only
package.jsonand the purify-edge entry inpackage-lock.jsonchange.npm run test:purify-edgepasses on this branch: 888 assertions in the main pass and 425 in the sinks pass, none failing.