fix: report fatalError when doctype is inside elements#550
Merged
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #550 +/- ##
==========================================
+ Coverage 92.77% 93.88% +1.10%
==========================================
Files 7 8 +1
Lines 2035 2044 +9
Branches 530 531 +1
==========================================
+ Hits 1888 1919 +31
+ Misses 147 125 -22
☔ View full report in Codecov by Sentry. |
- `hasInsertableNodeType` now checks for `CharacterData` nodes instead of only text nodes
- wrap DOMExceptions in ParseError in sax parser
and allow current and modern constructor arguments for DOMException
and cover more DOMException cases
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
karfau
added
xml:not well-formed
This was referenced Sep 26, 2024
karfau
added a commit
that referenced
this pull request
Oct 13, 2024
as part of #550 ("drop redundant and broken `Element.appendChild` implementation") the `_onUpdateChild` was not passed the added child, so the `childNodes` were re-indexed from the `firstChild` each time a node was appended. Now that the added child is being passed, the performance in 0.9.0 is still not as good as in 0.8.*, but this is because of the higher amount of checks being executed before adding a node. fixes #748
karfau
added a commit
that referenced
this pull request
Oct 13, 2024
as part of #550 ("drop redundant and broken `Element.appendChild` implementation") the `_onUpdateChild` was not passed the added child, so the `childNodes` were "re-indexed" from the `firstChild` each time a node was appended. This is why the performance degraded significantly, when there are a lot of childNodes to be appended. fixes #748
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.
which is a regression compared to 0.8.x, most likely introduced as part of #498
parseDoctypeCommentOrCDataElement.appendChildimplementationhasInsertableNodeTypenow checks forCharacterDatanodes instead of only text nodesDOMExceptions inParseErrorin sax parser