0.9.0-beta.11

Commits

Fixed

• report more non well-formed cases #519 / #45 / #125 / #467
  BREAKING-CHANGE: Reports more not well-formed documents as fatalError
  and drop broken support for optional and unclosed tags in HTML.

Other

• Translate/drop non English comments #518
• use node v16 for development #517

Thank you, @brodybits, @cbettinger, @josecarlosrx, for your contributions

0.9.0-beta.10

Commits

Fixed

• dom: prevent iteration over deleted items #514/ #499

Chore

• use prettier plugin for jsdoc #513

Thank you, @qtow, @shunkica, @homer0, for your contributions

0.8.10

Commits

Fixed

• dom: prevent iteration over deleted items #514/ #499

Thank you, @qtow, for your contributions

0.7.13

Commits

Fixed

• dom: prevent iteration over deleted items #514/ #499

Thank you, @qtow, for your contributions

0.9.0-beta.9

Commits

Fixed

• Set nodeName property in ProcessingInstruction #509 / #505
• preserve DOCTYPE internal subset #498 / #497 / #117
  BREAKING CHANGES: Many documents that were previously accepted by xmldom, esecially non well-formed ones are no longer accepted. Some issues that were formerly reported as errors are now a fatalError.
• DOMParser: Align parseFromString errors with specs #454

Chore

• stop running mutation tests using stryker #496
• make toErrorSnapshot windows compatible #503

Thank you, @cjbarth, @shunkica, @pmahend1, @niklasl, for your contributions

0.8.9

Commits

Fixed

• Set nodeName property in ProcessingInstruction #509 / #505

Thank you, @cjbarth, for your contributions

0.7.12

Commits

Fixed

• Set nodeName property in ProcessingInstruction #509 / #505

Thank you, @cjbarth, for your contributions

0.9.0-beta.8

Commits

Fixed

• Throw DOMException when calling removeChild with invalid parameter #494 / #135

BREAKING CHANGE: Previously it was possible (but not documented) to call Node.removeChild with any node in the tree,
and with certain exceptions, it would work. This is no longer the case: calling Node.removeChild with an argument that is not a direct child of the node that it is called from, will throw a NotFoundError DOMException, as it is described by the specs.

Thank you, @noseworthy, @davidmc24, for your contributions

0.9.0-beta.7

Commits

Feature

• Add compareDocumentPosition method from level 3 spec. #488

Fixed

• getAttribute and getAttributeNS should return null (#477) #46
• several issues in NamedNodeMap and Element (#482) #46
• properly parse closing where the last attribute has no value #485 / #486
• extend list of HTML entities #489

BREAKING CHANGE: Iteration over attributes now happens in the right order and non-existing attributes now return null instead of undefined. THe same is true for the namepsaceURI and prefix of Attr nodes.
All of the changes are fixing misalignment with the DOM specs, so if you expected it to work as specified,
nothing should break for you.

Chore

• update multiple devDependencies
• Configure jest (correctly) and wallaby #481 / #483

Thank you, @bulandent, @zorkow, for your contributions

0.8.8

Commits

Fixed

• extend list of HTML entities #489

Thank you, @zorkow, for your contributions