All notable changes to this project will be documented in this file.
This project adheres to Semantic Versioning.
nodeType values to public interface description #396#317> as specified #395Object.assign ponyfill #379#378Thank you @niklasl, @cburatto, @SheetJSDev, @pyrsmk for your contributions
#374#365#366#358, #376#360\n before parsing takes place and will no longer be preserved.
#284 / #310 \
BREAKING CHANGE: If you relied on the not spec compliant preservation of literal \t, \n or \r in attribute values.
To preserve those you will have to create XML that instead contains the correct numerical (or hexadecimal) equivalent (e.g. 	, 
, 
).DOMImplementation and XMLSerializer from lib/dom-parser.js #53 / #309
BREAKING CHANGE: Use the one provided by the main package export.removeChild #343 / #355#325#111 / #304Thank you @marrus-sh, @victorandree, @mdierolf, @tsabbay, @fatihpense for your contributions
__prototype__ attributes #315
Thank you @dsimpsonOMF#277 / #301#294
Thank you @rrthomas#233#302#300#297#292#279Due to #271 this version was published as
xmldom package to github (git tags 0.7.0 and 0.7.0+unscoped)@xmldom/xmldom package to npm (git tag 0.7.0+scoped)
For more details look at #278CVE-2021-32796Document.getElementsByClassName as specified #213, thank you @ChALkeR#268#267DOMImplementation according to recent specs #210#244#168 released in 0.6.0)localName as part of Document.createElement #229, thank you @rrthomasxmlns:ds="" #168< to < when serializing attribute values #198 / #199Avoid misinterpretation of malicious XML input - GHSA-h6q6-9hqw-rwfv (CVE-2021-21366)
DOMParser.errorHandler before parsing, to handle those errors differently.To accomplish this and also be able to verify it in tests I needed to
Error type ParseError and export itParseError from errorHandler.fatalError and prevent those from being caught in XMLReader.DOMHandler constructor as __DOMHandlerpublicId and systemId as is, including any quotes.
BREAKING CHANGE: If somebody relies on the actual unquoted values of those ids, they will need to take care of either single or double quotes and the right escaping.
(Without this change this would not have been possible because the SAX parser already dropped the information about the quotes that have been used in the source.)https://www.w3.org/TR/2006/REC-xml11-20060816/#dtd https://www.w3.org/TR/2006/REC-xml11-20060816/#IDAX1KS (External Entity Declaration)
Fix breaking preprocessors' directives when parsing attributes #171
fix(dom): Escape ]]> when serializing CharData #181
Switch to (only) MIT license (drop problematic LGPL license option) #178
Export DOMException; remove custom assertions; etc. #174
readme.md #188 behavior from v0.1.27 #67#113#156#144#91#84#66#63#78#104#79#81#70#77#64#106#107vows tests, drop proof tests #59#114xmltest cases #112#108#86component.json (deprecated package manager https://github.com/componentjs/guide)lib subdirectory.files entry in package.json and remove use of .npmignore.Document.getElementsByClassName.Node to the list of exportsentityMap.homepage, repository and bugs URLs in package.json.xmldom-alpha@v0.1.28 by the original authors.Object.create check from the _extends method of dom.js that added a __proto__ property ().__proto__ propertypackage.jsonThe patch versions (v0.1.29 - v0.1.31) that have been released on the v0.1.x branch, to reflect the changed maintainers, are branched off from v0.1.27 so they don't include the breaking changes introduced in xmldom-alpha@v0.1.28:
After the last commit to the original repository https://github.com/jindw/xmldom on the 9th of May 2017, the first commit to https://github.com/xmldom/xmldom is from the 19th of December 2019. The fork has been announced in the original repository on the 2nd of March 2020.
The versions listed below have been published to one or both of the following packages:
It is currently not planned to continue publishing the xmldom-alpha package.
The new maintainers did not invest time to understand changes that led to the last xmldom version 0.1.27 published by the original maintainer, but consider it the basis for their work.
A timeline of all the changes that happened from that version until 0.3.0 is available in https://github.com/xmldom/xmldom/issues/62. Any related questions should be asked there.
Published by @jindw on the 9th of May 2017 as
xmldom-alpha@0.1.28
BREAKING includes regression regarding (issue #57)
Fix dom.js serialization issue for missing document element (example that failed on toString() before this change)
Add new module entities.js
Published by @jindw on the 28th of Nov 2016 as
xmldom@0.1.27xmldom-alpha@0.1.27
Various bug fixes.
Published on the 18th of Nov 2016
as xmldom@0.1.26
Published on the 18th of Nov 2016 as
xmldom@0.1.25
Details unknown
Published on the 27th of November 2016 as
xmldom@0.1.24xmldom-alpha@0.1.24
Added node filter.
Published on the 5th of May 2016 as
xmldom-alpha@0.1.23
Add namespace support for nest node serialize.
Various other bug fixes.
* NS support for getElementsByTagNameNS.ns support.Details missing for this and potential earlier version
component.json #52.