Based on @xmldom/xmldom with some minor enhancements. Add querySelector, querySelectorAll and match method to Document and Element.
npm install xmldom-qsaThis is based on xmldom with some minor enhancements.
xmldom-qsa add querySelector, querySelectorAll and match method to Document and Element. And you can write some more methods to these elements by add prototype methods to Node.
xmldom is a javascript ponyfill to provide the following APIs that are present in modern browsers to other runtimes:
- convert an XML string into a DOM tree
```
new DOMParser().parseFromString(xml, mimeType) => Document
`
- create, access and modify a DOM tree
`
new DOMImplementation().createDocument(...) => Document
`
- serialize a DOM tree back into an XML string
`
new XMLSerializer().serializeToString(node) => string
The target runtimes xmldom supports are currently Node >= v10 (ES5) and Rhino (not tested as part of CI).
When deciding how to fix bugs or implement features, xmldom tries to stay as close as possible to the various related specifications/standards.0.
As indicated by the version starting with , this implementation is not feature complete and some implemented features differ from what the specifications describe.
Issues and PRs for such differences are always welcome, even when they only provide a failing test case.
This project was forked from it's original source in 2019, more details about that transition can be found in the CHANGELOG.
> npm install xmldom-qsa
Enhancements:
====
`javascript
doc.documentElement.querySelector('.clazz');
var Node = require('xmldom-qsa/dom').Node;
Node.prototype.addAttr = function(x,y) { ... }
doc.documentElement.addAttr('x','y');
`
In NodeJS
`javascript
const { DOMParser } = require('xmldom-qsa')
const doc = new DOMParser().parseFromString(
'
'\t
'\t
'\t
'
'text/xml'
)
doc.documentElement.setAttribute('x', 'y')
doc.documentElement.setAttributeNS('./lite', 'c:x', 'y2')
console.info(doc)
const nsAttr = doc.documentElement.getAttributeNS('./lite', 'x')
console.info(nsAttr)
`
Note: in Typescript ~and ES6~(see #316) you can use the import approach, as follows:
`javascript`
import { DOMParser } from 'xmldom-qsa'
* DOMParser:
`javascript`
parseFromString(xmlsource,mimeType)
* options extension _by xmldom_ (not DOM standard!!)
`javascript
//added the options argument
new DOMParser(options)
//errorHandler is supported
new DOMParser({
/**
* locator is always need for error position info
*/
locator:{},
/**
* you can override the errorHandler for xml parser
* @link http://www.saxproject.org/apidoc/org/xml/sax/ErrorHandler.html
*/
errorHandler:{warning:function(w){console.warn(w)},error:callback,fatalError:callback}
//only callback model
//errorHandler:function(level,msg){console.log(level,msg)}
})
`
`javascript`
serializeToString(node)
$3
* Node
readonly class properties (aka NodeType),Node
these can be accessed from any instance node:if (node.nodeType === node.ELEMENT_NODE) {...
1. ELEMENT_NODE (1)ATTRIBUTE_NODE
2. (2)TEXT_NODE
3. (3)CDATA_SECTION_NODE
4. (4)ENTITY_REFERENCE_NODE
5. (5)ENTITY_NODE
6. (6)PROCESSING_INSTRUCTION_NODE
7. (7)COMMENT_NODE
8. (8)DOCUMENT_NODE
9. (9)DOCUMENT_TYPE_NODE
10. (10)DOCUMENT_FRAGMENT_NODE
11. (11)NOTATION_NODE
12. (12)
attribute:
- nodeValue | prefix
readonly attribute:
- nodeName | nodeType | parentNode | childNodes | firstChild | lastChild | previousSibling | nextSibling | attributes | ownerDocument | namespaceURI | localName
method:
* insertBefore(newChild, refChild)replaceChild(newChild, oldChild)
* removeChild(oldChild)
* appendChild(newChild)
* hasChildNodes()
* cloneNode(deep)
* normalize()
* isSupported(feature, version)
* hasAttributes()
*
* DOMException
extends the Error type thrown as part of DOM API.
readonly class properties:
- INDEX_SIZE_ERR (1)DOMSTRING_SIZE_ERR
- (2)HIERARCHY_REQUEST_ERR
- (3)WRONG_DOCUMENT_ERR
- (4)INVALID_CHARACTER_ERR
- (5)NO_DATA_ALLOWED_ERR
- (6)NO_MODIFICATION_ALLOWED_ERR
- (7)NOT_FOUND_ERR
- (8)NOT_SUPPORTED_ERR
- (9)INUSE_ATTRIBUTE_ERR
- (10)INVALID_STATE_ERR
- (11)SYNTAX_ERR
- (12)INVALID_MODIFICATION_ERR
- (13)NAMESPACE_ERR
- (14)INVALID_ACCESS_ERR
- (15)
attributes:
- code with a value matching one of the above constants.
method:
- hasFeature(feature, version)createDocumentType(qualifiedName, publicId, systemId)
- createDocument(namespaceURI, qualifiedName, doctype)
-
* Document : Node
readonly attribute:
- doctype | implementation | documentElement
method:
- createElement(tagName)createDocumentFragment()
- createTextNode(data)
- createComment(data)
- createCDATASection(data)
- createProcessingInstruction(target, data)
- createAttribute(name)
- createEntityReference(name)
- getElementsByTagName(tagname)
- importNode(importedNode, deep)
- createElementNS(namespaceURI, qualifiedName)
- createAttributeNS(namespaceURI, qualifiedName)
- getElementsByTagNameNS(namespaceURI, localName)
- getElementById(elementId)
-
* DocumentFragment : Node
* Element : Node
readonly attribute:
- tagName
method:
- getAttribute(name)setAttribute(name, value)
- removeAttribute(name)
- getAttributeNode(name)
- setAttributeNode(newAttr)
- removeAttributeNode(oldAttr)
- getElementsByTagName(name)
- getAttributeNS(namespaceURI, localName)
- setAttributeNS(namespaceURI, qualifiedName, value)
- removeAttributeNS(namespaceURI, localName)
- getAttributeNodeNS(namespaceURI, localName)
- setAttributeNodeNS(newAttr)
- getElementsByTagNameNS(namespaceURI, localName)
- hasAttribute(name)
- hasAttributeNS(namespaceURI, localName)
-
* Attr : Node
attribute:
- value
readonly attribute:
- name | specified | ownerElement
* NodeList
readonly attribute:
- length
method:
- item(index)
readonly attribute:
- length
method:
- getNamedItem(name)setNamedItem(arg)
- removeNamedItem(name)
- item(index)
- getNamedItemNS(namespaceURI, localName)
- setNamedItemNS(arg)
- removeNamedItemNS(namespaceURI, localName)
-
* CharacterData : Node
method:
- substringData(offset, count)appendData(arg)
- insertData(offset, arg)
- deleteData(offset, count)
- replaceData(offset, count, arg)
-
* Text : CharacterData
method:
- splitText(offset)
* CDATASection
* Comment : CharacterData
readonly attribute:
- name | entities | notations | publicId | systemId | internalSubset
* Notation : Node
readonly attribute:
- publicId | systemId
* Entity : Node
readonly attribute:
- publicId | systemId | notationName
* EntityReference : Node
* ProcessingInstruction : Node
attribute:
- datatarget
readonly attribute:
-
* Node
attribute:
- textContent
method:
- isDefaultNamespace(namespaceURI)lookupNamespaceURI(prefix)
-
* [Node] Source position extension;
attribute:
- lineNumber //number starting from 1columnNumber
- //number starting from 1
The implementation is based on several specifications:
!Overview of related specifications and their relations
From the W3C DOM Parsing and Serialization (WD 2016) xmldom provides an implementation for the interfaces:DOMParser
- XMLSerializer
-
Note that there are some known deviations between this implementation and the W3 specifications.
Note: The latest version of this spec has the status "Editors Draft", since it is under active development. One major change is that the definition of the DOMParser interface has been moved to the HTML spec
The original author claims that xmldom implements [DOM Level 2] in a "fully compatible" way and some parts of [DOM Level 3], but there are not enough tests to prove this. Both Specifications are now superseded by the [DOM Level 4 aka Living standard] wich has a much broader scope than xmldom.
xmldom implements the following interfaces (most constructors are currently not exposed):
- AttrCDATASection
- CharacterData
- Comment
- Document
- DocumentFragment
- DocumentType
- DOMException
- (constructor exposed)DOMImplementation
- (constructor exposed)Element
- Entity
- EntityReference
- LiveNodeList
- NamedNodeMap
- Node
- (constructor exposed)NodeList
- Notation
- ProcessingInstruction
- Text
-
more details are available in the (incomplete) API Reference section.
xmldom does not have any goal of supporting the full spec, but it has some capability to parse, report and serialize things differently when "detecting HTML" (by checking the default namespace).
There is an upcoming change to better align the implementation with the latest specs, related to
xmldom has an own SAX parser implementation to do the actual parsing, which implements some interfaces in alignment with the Java interfaces SAX defines:
- XMLReaderDOMHandler`
-
There is an idea/proposal to make it possible to replace it with something else in