Skip to content

Releases: xmldom/xmldom

0.7.11

30 May 19:13
0.7.11
44477fc
Compare
Choose a tag to compare

Commits

Fixed

  • extend list of HTML entities #489

Thank you, @zorkow, for your contributions

0.8.7

31 Mar 09:17
0.8.7
b69bbbe
Compare
Choose a tag to compare

Commits

Fixed

  • properly parse closing where the last attribute has no value #485 / #486

Thank you, @bulandent, for your contributions

0.7.10

31 Mar 08:53
0.7.10
f97cb3a
Compare
Choose a tag to compare

commits

Fixed

  • properly parse closing where the last attribute has no value #485 / #486

Thank you, @bulandent, for your contributions

0.8.6

05 Nov 09:58
0.8.6
238b1ea
Compare
Choose a tag to compare

Commits

Fixed

  • Properly check nodes before replacement #457 / #455 / #456

Thank you, @edemaine, @pedro-l9, for your contributions

0.7.9

05 Nov 10:12
0.7.9
927392f
Compare
Choose a tag to compare

Commits

Fixed

  • Properly check nodes before replacement #457 / #455 / #456

Thank you, @edemaine, @pedro-l9, for your contributions

0.9.0-beta.6

03 Nov 08:01
0.9.0-beta.6
4ca9991
Compare
Choose a tag to compare
0.9.0-beta.6 Pre-release
Pre-release

Commits

Fixed

  • Properly check nodes before replacement #457 / #455

Thank you, @edemaine, @pedro-l9, for your contributions

0.9.0-beta.5

31 Oct 08:39
0.9.0-beta.5
784786b
Compare
Choose a tag to compare
0.9.0-beta.5 Pre-release
Pre-release

Commits

Fixed

Thank you, @fengxinming, for your contributions

0.8.5

31 Oct 08:57
0.8.5
afc57ec
Compare
Choose a tag to compare

Commits

Fixed

  • fix: Restore ES5 compatibility #452 / #453

Thank you, @fengxinming, for your contributions

0.7.8

31 Oct 16:22
0.7.8
0d6e3a1
Compare
Choose a tag to compare

Commits

Fixed

  • fix: Restore ES5 compatibility #452 / #453

Thank you, @fengxinming, for your contributions

0.9.0-beta.4

29 Oct 21:43
0.9.0-beta.4
39bc1fc
Compare
Choose a tag to compare
0.9.0-beta.4 Pre-release
Pre-release

Commits

Fixed

  • Security: Prevent inserting DOM nodes when they are not well-formed CVE-2022-39353
    In case such a DOM would be created, the part that is not well-formed will be transformed into text nodes, in which xml specific characters like < and > are encoded accordingly.
    In the upcoming version 0.9.0 those text nodes will no longer be added and an error will be thrown instead.
    This change can break your code, if you relied on this behavior, e.g. multiple root elements in the past. We consider it more important to align with the specs that we want to be aligned with, considering the potential security issues that might derive from people not being aware of the difference in behavior.
    Related Spec: https://dom.spec.whatwg.org/#concept-node-ensure-pre-insertion-validity

Chore

  • update multiple devDependencies
  • Add eslint-plugin-node for lib #448 / #190
  • style: Apply prettier to all code #447 / #29 / #130

Thank you, @XhmikosR, @awwright, @frumioj, @cjbarth, @markgollnick for your contributions