Table of contents

Appendices

1.4 Fundamental Interfaces: Core Module

The interfaces within this section are considered fundamental, and must be fully implemented by all conforming implementations of the DOM, including all HTML DOM implementations [DOM2HTML], unless otherwise specified.

A DOM application may use the DOMImplementation.hasFeature(feature, version) method with parameter values "Core" and "3.0" (respectively) to determine whether or not this module is supported by the implementation. Any implementation that conforms to DOM Level 3 or a DOM Level 3 module must conform to the Core module. Please refer to additional information about [conformance] in this specification. The DOM Level 3 Core module is backward compatible with the DOM Level 2 Core [DOM2Core] module, i.e. a DOM Level 3 Core implementation who returns true for "Core" with the version number "3.0" must also return true for this feature when the version number is "2.0", "" or, null.

DOM operations only raise exceptions in "exceptional" circumstances, i.e., when an operation is impossible to perform (either for logical reasons, because data is lost, or because the implementation has become unstable). In general, DOM methods return specific error values in ordinary processing situations, such as out-of-bound errors when using NodeList.

Implementations should raise other exceptions under other circumstances. For example, implementations should raise an implementation-dependent exception if a null argument is passed when null was not expected.

Some languages and object systems do not support the concept of exceptions. For such systems, error conditions may be indicated using native error reporting mechanisms. For some bindings, for example, methods may return error codes similar to those listed in the corresponding method descriptions.

An integer indicating the type of error generated.

NOTE: 

Other numeric codes are reserved for W3C for possible future use.

If index or size is negative, or greater than the allowed value.

If the specified range of text does not fit into a DOMString.

If any Node is inserted somewhere it doesn't belong.

If a Node is used in a different document than the one that created it (that doesn't support it).

If an invalid or illegal character is specified, such as in an XML name.

If data is specified for a Node which does not support data.

If an attempt is made to modify an object where modifications are not allowed.

If an attempt is made to reference a Node in a context where it does not exist.

If the implementation does not support the requested type of object or operation.

If an attempt is made to add an attribute that is already in use elsewhere.

If an attempt is made to use an object that is not, or is no longer, usable.

If an invalid or illegal string is specified.

If an attempt is made to modify the type of the underlying object.

If an attempt is made to create or change an object in a way which is incorrect with regard to namespaces.

If a parameter or an operation is not supported by the underlying object.

If a call to a method such as insertBefore or removeChild would make the Node invalid with respect to "partial validity", this exception would be raised and the operation would not be done. This code is used in [DOMVal]. Refer to this specification for further information.

If the type of an object is incompatible with the expected type of the parameter associated to the object.

The DOMStringList interface provides the abstraction of an ordered collection of DOMString values, without defining or constraining how this collection is implemented. The items in the DOMStringList are accessible via an integral index, starting from 0.

Returns the indexth item in the collection. If index is greater than or equal to the number of DOMStrings in the list, this returns null.

Index into the collection.

The DOMString at the indexth position in the DOMStringList, or null if that is not a valid index.

The number of DOMStrings in the list. The range of valid child node indices is 0 to length-1 inclusive.

Test if a string is part of this DOMStringList.

The string to look for.

true if the string has been found, false otherwise.

The NameList interface provides the abstraction of an ordered collection of parallel pairs of name and namespace values (which could be null values), without defining or constraining how this collection is implemented. The items in the NameList are accessible via an integral index, starting from 0.

Returns the indexth name item in the collection.

Index into the collection.

The name at the indexth position in the NameList, or null if there is no name for the specified index or if the index is out of range.

Returns the indexth namespaceURI item in the collection.

Index into the collection.

The namespace URI at the indexth position in the NameList, or null if there is no name for the specified index or if the index is out of range.

The number of pairs (name and namespaceURI) in the list. The range of valid child node indices is 0 to length-1 inclusive.

Test if a name is part of this NameList.

The name to look for.

true if the name has been found, false otherwise.

Test if the pair namespaceURI/name is part of this NameList.

The namespace URI to look for.

The name to look for.

true if the pair namespaceURI/name has been found, false otherwise.

The DOMImplementationList interface provides the abstraction of an ordered collection of DOM implementations, without defining or constraining how this collection is implemented. The items in the DOMImplementationList are accessible via an integral index, starting from 0.

Returns the indexth item in the collection. If index is greater than or equal to the number of DOMImplementations in the list, this returns null.

Index into the collection.

The DOMImplementation at the indexth position in the DOMImplementationList, or null if that is not a valid index.

The number of DOMImplementations in the list. The range of valid child node indices is 0 to length-1 inclusive.

This interface permits a DOM implementer to supply one or more implementations, based upon requested features and versions, as specified in [DOM Features]. Each implemented DOMImplementationSource object is listed in the binding-specific list of available sources so that its DOMImplementation objects are made available.

A method to request the first DOM implementation that supports the specified features.

A string that specifies which features and versions are required. This is a space separated list in which each feature is specified by its name optionally followed by a space and a version number.

This method returns the first item of the list returned by getDOMImplementationList.

As an example, the string "XML 3.0 Traversal +Events 2.0" will request a DOM implementation that supports the module "XML" for its 3.0 version, a module that support of the "Traversal" module for any version, and the module "Events" for its 2.0 version. The module "Events" must be accessible using the method Node.getFeature() and DOMImplementation.getFeature().

The first DOM implementation that support the desired features, or null if this source has none.

A method to request a list of DOM implementations that support the specified features and versions, as specified in [DOM Features].

A string that specifies which features and versions are required. This is a space separated list in which each feature is specified by its name optionally followed by a space and a version number. This is something like: "XML 3.0 Traversal +Events 2.0"

A list of DOM implementations that support the desired features.

The DOMImplementation interface provides a number of methods for performing operations that are independent of any particular instance of the document object model.

Test if the DOM implementation implements a specific feature and version, as specified in [DOM Features].

The name of the feature to test.

This is the version number of the feature to test.

true if the feature is implemented in the specified version, false otherwise.

Creates an empty DocumentType node. Entity declarations and notations are not made available. Entity reference expansions and default attribute additions do not occur..

The qualified name of the document type to be created.

The external subset public identifier.

The external subset system identifier.

A new DocumentType node with Node.ownerDocument set to null.

INVALID_CHARACTER_ERR: Raised if the specified qualified name is not an XML name according to [XML].

NAMESPACE_ERR: Raised if the qualifiedName is malformed.

NOT_SUPPORTED_ERR: May be raised if the implementation does not support the feature "XML" and the language exposed through the Document does not support XML Namespaces (such as [HTML40]).

Creates a DOM Document object of the specified type with its document element.

Note that based on the DocumentType given to create the document, the implementation may instantiate specialized Document objects that support additional features than the "Core", such as "HTML" [DOM2HTML]. On the other hand, setting the DocumentType after the document was created makes this very unlikely to happen. Alternatively, specialized Document creation methods, such as createHTMLDocument [DOM2HTML], can be used to obtain specific types of Document objects.

The namespace URI of the document element to create or null.

The qualified name of the document element to be created or null.

The type of document to be created or null.

When doctype is not null, its Node.ownerDocument attribute is set to the document being created.

A new Document object with its document element. If the NamespaceURI, qualifiedName, and doctype are null, the returned Document is empty with no document element.

INVALID_CHARACTER_ERR: Raised if the specified qualified name is not an XML name according to [XML].

NAMESPACE_ERR: Raised if the qualifiedName is malformed, if the qualifiedName has a prefix and the namespaceURI is null, or if the qualifiedName is null and the namespaceURI is different from null, or if the qualifiedName has a prefix that is "xml" and the namespaceURI is different from "http://www.w3.org/XML/1998/namespace" [Namespaces], or if the DOM implementation does not support the "XML" feature but a non-null namespace URI was provided, since namespaces were defined by XML.

WRONG_DOCUMENT_ERR: Raised if doctype has already been used with a different document or was created from a different implementation.

NOT_SUPPORTED_ERR: May be raised if the implementation does not support the feature "XML" and the language exposed through the Document does not support XML Namespaces (such as [HTML40]).

This method returns a specialized object which implements the specialized APIs of the specified feature and version, as specified in [DOM Features]. The specialized object may also be obtained by using binding-specific casting methods but is not necessarily expected to, as discussed in [Mixed DOM Implementations]. This method also allow the implementation to provide specialized objects which do not support the DOMImplementation interface.

The name of the feature requested. Note that any plus sign "+" prepended to the name of the feature will be ignored since it is not significant in the context of this method.

This is the version number of the feature to test.

Returns an object which implements the specialized APIs of the specified feature and version, if any, or null if there is no object which implements interfaces associated with that feature. If the DOMObject returned by this method implements the DOMImplementation interface, it must delegate to the primary core DOMImplementation and not return results inconsistent with the primary core DOMImplementation such as hasFeature, getFeature, etc.

DocumentFragment is a "lightweight" or "minimal" Document object. It is very common to want to be able to extract a portion of a document's tree or to create a new fragment of a document. Imagine implementing a user command like cut or rearranging a document by moving fragments around. It is desirable to have an object which can hold such fragments and it is quite natural to use a Node for this purpose. While it is true that a Document object could fulfill this role, a Document object can potentially be a heavyweight object, depending on the underlying implementation. What is really needed for this is a very lightweight object. DocumentFragment is such an object.

Furthermore, various operations -- such as inserting nodes as children of another Node -- may take DocumentFragment objects as arguments; this results in all the child nodes of the DocumentFragment being moved to the child list of this node.

The children of a DocumentFragment node are zero or more nodes representing the tops of any sub-trees defining the structure of the document. DocumentFragment nodes do not need to be well-formed XML documents (although they do need to follow the rules imposed upon well-formed XML parsed entities, which can have multiple top nodes). For example, a DocumentFragment might have only one child and that child node could be a Text node. Such a structure model represents neither an HTML document nor a well-formed XML document.

When a DocumentFragment is inserted into a Document (or indeed any other Node that may take children) the children of the DocumentFragment and not the DocumentFragment itself are inserted into the Node. This makes the DocumentFragment very useful when the user wishes to create nodes that are siblings; the DocumentFragment acts as the parent of these nodes so that the user can use the standard methods from the Node interface, such as Node.insertBefore and Node.appendChild.

The Document interface represents the entire HTML or XML document. Conceptually, it is the root of the document tree, and provides the primary access to the document's data.

Since elements, text nodes, comments, processing instructions, etc. cannot exist outside the context of a Document, the Document interface also contains the factory methods needed to create these objects. The Node objects created have a ownerDocument attribute which associates them with the Document within whose context they were created.

The Document Type Declaration (see DocumentType) associated with this document. For XML documents without a document type declaration this returns null. For HTML documents, a DocumentType object may be returned, independently of the presence or absence of document type declaration in the HTML document.

This provides direct access to the DocumentType node, child node of this Document. This node can be set at document creation time and later changed through the use of child nodes manipulation methods, such as Node.insertBefore, or Node.replaceChild. Note, however, that while some implementations may instantiate different types of Document objects supporting additional features than the "Core", such as "HTML" [DOM2HTML], based on the DocumentType specified at creation time, changing it afterwards is very unlikely to result in a change of the features supported.

The DOMImplementation object that handles this document. A DOM application may use objects from multiple implementations.

This is a convenience attribute that allows direct access to the child node that is the document element of the document.

Creates an element of the type specified. Note that the instance returned implements the Element interface, so attributes can be specified directly on the returned object.

In addition, if there are known attributes with default values, Attr nodes representing them are automatically created and attached to the element.

To create an element with a qualified name and namespace URI, use the createElementNS method.

The name of the element type to instantiate. For XML, this is case-sensitive, otherwise it depends on the case-sensitivity of the markup language in use. In that case, the name is mapped to the canonical form of that markup by the DOM implementation.

A new Element object with the nodeName attribute set to tagName, and localName, prefix, and namespaceURI set to null.

INVALID_CHARACTER_ERR: Raised if the specified name is not an XML name according to the XML version in use specified in the Document.xmlVersion attribute.

Creates an empty DocumentFragment object.

A new DocumentFragment.

Creates a Text node given the specified string.

The data for the node.

The new Text object.

Creates a Comment node given the specified string.

The data for the node.

The new Comment object.

Creates a CDATASection node whose value is the specified string.

The data for the CDATASection contents.

The new CDATASection object.

NOT_SUPPORTED_ERR: Raised if this document is an HTML document.

Creates a ProcessingInstruction node given the specified name and data strings.

The target part of the processing instruction.

Unlike Document.createElementNS or Document.createAttributeNS, no namespace well-formed checking is done on the target name. Applications should invoke Document.normalizeDocument() with the parameter "namespaces" set to true in order to ensure that the target name is namespace well-formed.

The data for the node.

The new ProcessingInstruction object.

INVALID_CHARACTER_ERR: Raised if the specified target is not an XML name according to the XML version in use specified in the Document.xmlVersion attribute.

NOT_SUPPORTED_ERR: Raised if this document is an HTML document.

Creates an Attr of the given name. Note that the Attr instance can then be set on an Element using the setAttributeNode method.

To create an attribute with a qualified name and namespace URI, use the createAttributeNS method.

The name of the attribute.

A new Attr object with the nodeName attribute set to name, and localName, prefix, and namespaceURI set to null. The value of the attribute is the empty string.

INVALID_CHARACTER_ERR: Raised if the specified name is not an XML name according to the XML version in use specified in the Document.xmlVersion attribute.

Creates an EntityReference object. In addition, if the referenced entity is known, the child list of the EntityReference node is made the same as that of the corresponding Entity node.

NOTE: 

If any descendant of the Entity node has an unbound namespace prefix, the corresponding descendant of the created EntityReference node is also unbound; (its namespaceURI is null). The DOM Level 2 and 3 do not support any mechanism to resolve namespace prefixes in this case.

The name of the entity to reference.

Unlike Document.createElementNS or Document.createAttributeNS, no namespace well-formed checking is done on the entity name. Applications should invoke Document.normalizeDocument() with the parameter "namespaces" set to true in order to ensure that the entity name is namespace well-formed.

The new EntityReference object.

INVALID_CHARACTER_ERR: Raised if the specified name is not an XML name according to the XML version in use specified in the Document.xmlVersion attribute.

NOT_SUPPORTED_ERR: Raised if this document is an HTML document.

Returns a NodeList of all the Elements in document order with a given tag name and are contained in the document.

The name of the tag to match on. The special value "*" matches all tags. For XML, the tagname parameter is case-sensitive, otherwise it depends on the case-sensitivity of the markup language in use.

A new NodeList object containing all the matched Elements.

Imports a node from another document to this document, without altering or removing the source node from the original document; this method creates a new copy of the source node. The returned node has no parent; (parentNode is null).

For all nodes, importing a node creates a node object owned by the importing document, with attribute values identical to the source node's nodeName and nodeType, plus the attributes related to namespaces (prefix, localName, and namespaceURI). As in the cloneNode operation, the source node is not altered. User data associated to the imported node is not carried over. However, if any UserDataHandlers has been specified along with the associated data these handlers will be called with the appropriate parameters before this method returns.

Additional information is copied as appropriate to the nodeType, attempting to mirror the behavior expected if a fragment of XML or HTML source was copied from one document to another, recognizing that the two documents may have different DTDs in the XML case. The following list describes the specifics for each type of node.

ATTRIBUTE_NODE

The ownerElement attribute is set to null and the specified flag is set to true on the generated Attr. The descendants of the source Attr are recursively imported and the resulting nodes reassembled to form the corresponding subtree.

Note that the deep parameter has no effect on Attr nodes; they always carry their children with them when imported.

DOCUMENT_FRAGMENT_NODE

If the deep option was set to true, the descendants of the source DocumentFragment are recursively imported and the resulting nodes reassembled under the imported DocumentFragment to form the corresponding subtree. Otherwise, this simply generates an empty DocumentFragment.

DOCUMENT_NODE

Document nodes cannot be imported.

DOCUMENT_TYPE_NODE

DocumentType nodes cannot be imported.

ELEMENT_NODE

Specified attribute nodes of the source element are imported, and the generated Attr nodes are attached to the generated Element. Default attributes are not copied, though if the document being imported into defines default attributes for this element name, those are assigned. If the importNode deep parameter was set to true, the descendants of the source element are recursively imported and the resulting nodes reassembled to form the corresponding subtree.

ENTITY_NODE

Entity nodes can be imported, however in the current release of the DOM the DocumentType is readonly. Ability to add these imported nodes to a DocumentType will be considered for addition to a future release of the DOM.

On import, the publicId, systemId, and notationName attributes are copied. If a deep import is requested, the descendants of the the source Entity are recursively imported and the resulting nodes reassembled to form the corresponding subtree.

ENTITY_REFERENCE_NODE

Only the EntityReference itself is copied, even if a deep import is requested, since the source and destination documents might have defined the entity differently. If the document being imported into provides a definition for this entity name, its value is assigned.

NOTATION_NODE

Notation nodes can be imported, however in the current release of the DOM the DocumentType is readonly. Ability to add these imported nodes to a DocumentType will be considered for addition to a future release of the DOM.

On import, the publicId and systemId attributes are copied.

Note that the deep parameter has no effect on this type of nodes since they cannot have any children.

PROCESSING_INSTRUCTION_NODE

The imported node copies its target and data values from those of the source node.

Note that the deep parameter has no effect on this type of nodes since they cannot have any children.

TEXT_NODE, CDATA_SECTION_NODE, COMMENT_NODE

These three types of nodes inheriting from CharacterData copy their data and length attributes from those of the source node.

Note that the deep parameter has no effect on these types of nodes since they cannot have any children.

The node to import.

If true, recursively import the subtree under the specified node; if false, import only the node itself, as explained above. This has no effect on nodes that cannot have any children, and on Attr, and EntityReference nodes.

The imported node that belongs to this Document.

NOT_SUPPORTED_ERR: Raised if the type of node being imported is not supported.

INVALID_CHARACTER_ERR: Raised if one of the imported names is not an XML name according to the XML version in use specified in the Document.xmlVersion attribute. This may happen when importing an XML 1.1 [XML11] element into an XML 1.0 document, for instance.

Creates an element of the given qualified name and namespace URI.

Per [Namespaces], applications must use the value null as the namespaceURI parameter for methods if they wish to have no namespace.

The namespace URI of the element to create.

The qualified name of the element type to instantiate.

A new Element object with the following attributes:

INVALID_CHARACTER_ERR: Raised if the specified qualifiedName is not an XML name according to the XML version in use specified in the Document.xmlVersion attribute.

NAMESPACE_ERR: Raised if the qualifiedName is a malformed qualified name, if the qualifiedName has a prefix and the namespaceURI is null, or if the qualifiedName has a prefix that is "xml" and the namespaceURI is different from "http://www.w3.org/XML/1998/namespace" [Namespaces], or if the qualifiedName or its prefix is "xmlns" and the namespaceURI is different from "http://www.w3.org/2000/xmlns/", or if the namespaceURI is "http://www.w3.org/2000/xmlns/" and neither the qualifiedName nor its prefix is "xmlns".

NOT_SUPPORTED_ERR: Always thrown if the current document does not support the "XML" feature, since namespaces were defined by XML.

Creates an attribute of the given qualified name and namespace URI.

Per [Namespaces], applications must use the value null as the namespaceURI parameter for methods if they wish to have no namespace.

The namespace URI of the attribute to create.

The qualified name of the attribute to instantiate.

A new Attr object with the following attributes:

INVALID_CHARACTER_ERR: Raised if the specified qualifiedName is not an XML name according to the XML version in use specified in the Document.xmlVersion attribute.

NAMESPACE_ERR: Raised if the qualifiedName is a malformed qualified name, if the qualifiedName has a prefix and the namespaceURI is null, if the qualifiedName has a prefix that is "xml" and the namespaceURI is different from "http://www.w3.org/XML/1998/namespace", if the qualifiedName or its prefix is "xmlns" and the namespaceURI is different from "http://www.w3.org/2000/xmlns/", or if the namespaceURI is "http://www.w3.org/2000/xmlns/" and neither the qualifiedName nor its prefix is "xmlns".

NOT_SUPPORTED_ERR: Always thrown if the current document does not support the "XML" feature, since namespaces were defined by XML.

Returns a NodeList of all the Elements with a given local name and namespace URI in document order.

The namespace URI of the elements to match on. The special value "*" matches all namespaces.

The local name of the elements to match on. The special value "*" matches all local names.

A new NodeList object containing all the matched Elements.

Returns the Element that has an ID attribute with the given value. If no such element exists, this returns null. If more than one element has an ID attribute with that value, what is returned is undefined.

The DOM implementation is expected to use the attribute Attr.isId to determine if an attribute is of type ID.

NOTE: 

Attributes with the name "ID" or "id" are not of type ID unless so defined.

The unique id value for an element.

The matching element or null if there is none.

An attribute specifying the encoding used for this document at the time of the parsing. This is null when it is not known, such as when the Document was created in memory.

An attribute specifying, as part of the [XML declaration], the encoding of this document. This is null when unspecified or when it is not known, such as when the Document was created in memory.

An attribute specifying, as part of the [XML declaration], whether this document is standalone. This is false when unspecified.

NOTE: 

No verification is done on the value when setting this attribute. Applications should use Document.normalizeDocument() with the "validate" parameter to verify if the value matches the [validity constraint for standalone document declaration] as defined in [XML].

NOT_SUPPORTED_ERR: Raised if this document does not support the "XML" feature.

An attribute specifying, as part of the [XML declaration], the version number of this document. If there is no declaration and if this document supports the "XML" feature, the value is "1.0". If this document does not support the "XML" feature, the value is always null. Changing this attribute will affect methods that check for invalid characters in XML names. Application should invoke Document.normalizeDocument() in order to check for invalid characters in the Nodes that are already part of this Document.

DOM applications may use the DOMImplementation.hasFeature(feature, version) method with parameter values "XMLVersion" and "1.0" (respectively) to determine if an implementation supports [XML]. DOM applications may use the same method with parameter values "XMLVersion" and "1.1" (respectively) to determine if an implementation supports [XML11]. In both cases, in order to support XML, an implementation must also support the "XML" feature defined in this specification. Document objects supporting a version of the "XMLVersion" feature must not raise a NOT_SUPPORTED_ERR exception for the same version number when using Document.xmlVersion.

NOT_SUPPORTED_ERR: Raised if the version is set to a value that is not supported by this Document or if this document does not support the "XML" feature.

An attribute specifying whether error checking is enforced or not. When set to false, the implementation is free to not test every possible error case normally defined on DOM operations, and not raise any DOMException on DOM operations or report errors while using Document.normalizeDocument(). In case of error, the behavior is undefined. This attribute is true by default.

The location of the document or null if undefined or if the Document was created using DOMImplementation.createDocument. No lexical checking is performed when setting this attribute; this could result in a null value returned when using Node.baseURI.

Beware that when the Document supports the feature "HTML" [DOM2HTML], the href attribute of the HTML BASE element takes precedence over this attribute when computing Node.baseURI.

Attempts to adopt a node from another document to this document. If supported, it changes the ownerDocument of the source node, its children, as well as the attached attribute nodes if there are any. If the source node has a parent it is first removed from the child list of its parent. This effectively allows moving a subtree from one document to another (unlike importNode() which create a copy of the source node instead of moving it). When it fails, applications should use Document.importNode() instead. Note that if the adopted node is already part of this document (i.e. the source and target document are the same), this method still has the effect of removing the source node from the child list of its parent, if any. The following list describes the specifics for each type of node.

ATTRIBUTE_NODE

The ownerElement attribute is set to null and the specified flag is set to true on the adopted Attr. The descendants of the source Attr are recursively adopted.

DOCUMENT_FRAGMENT_NODE

The descendants of the source node are recursively adopted.

DOCUMENT_NODE

Document nodes cannot be adopted.

DOCUMENT_TYPE_NODE

DocumentType nodes cannot be adopted.

ELEMENT_NODE

Specified attribute nodes of the source element are adopted. Default attributes are discarded, though if the document being adopted into defines default attributes for this element name, those are assigned. The descendants of the source element are recursively adopted.

ENTITY_NODE

Entity nodes cannot be adopted.

ENTITY_REFERENCE_NODE

Only the EntityReference node itself is adopted, the descendants are discarded, since the source and destination documents might have defined the entity differently. If the document being imported into provides a definition for this entity name, its value is assigned.

NOTATION_NODE

Notation nodes cannot be adopted.

PROCESSING_INSTRUCTION_NODE, TEXT_NODE, CDATA_SECTION_NODE, COMMENT_NODE

These nodes can all be adopted. No specifics.

NOTE: 

Since it does not create new nodes unlike the Document.importNode() method, this method does not raise an INVALID_CHARACTER_ERR exception, and applications should use the Document.normalizeDocument() method to check if an imported name is not an XML name according to the XML version in use.

The node to move into this document.

The adopted node, or null if this operation fails, such as when the source node comes from a different implementation.

NOT_SUPPORTED_ERR: Raised if the source node is of type DOCUMENT, DOCUMENT_TYPE.

NO_MODIFICATION_ALLOWED_ERR: Raised when the source node is readonly.

The configuration used when Document.normalizeDocument() is invoked.

This method acts as if the document was going through a save and load cycle, putting the document in a "normal" form. As a consequence, this method updates the replacement tree of EntityReference nodes and normalizes Text nodes, as defined in the method Node.normalize().

Otherwise, the actual result depends on the features being set on the Document.domConfig object and governing what operations actually take place. Noticeably this method could also make the document namespace well-formed according to the algorithm described in [Namespace Normalization], check the character normalization, remove the CDATASection nodes, etc. See DOMConfiguration for details.

// Keep in the document the information defined
// in the XML Information Set (Java example)
DOMConfiguration docConfig = myDocument.getDomConfig();
docConfig.setParameter("infoset", Boolean.TRUE);
myDocument.normalizeDocument();

Mutation events, when supported, are generated to reflect the changes occurring on the document.

If errors occur during the invocation of this method, such as an attempt to update a read-only node or a Node.nodeName contains an invalid character according to the XML version in use, errors or warnings (DOMError.SEVERITY_ERROR or DOMError.SEVERITY_WARNING) will be reported using the DOMErrorHandler object associated with the "error-handler" parameter. Note this method might also report fatal errors (DOMError.SEVERITY_FATAL_ERROR) if an implementation cannot recover from an error.

Rename an existing node of type ELEMENT_NODE or ATTRIBUTE_NODE.

When possible this simply changes the name of the given node, otherwise this creates a new node with the specified name and replaces the existing node with the new node as described below.

If simply changing the name of the given node is not possible, the following operations are performed: a new node is created, any registered event listener is registered on the new node, any user data attached to the old node is removed from that node, the old node is removed from its parent if it has one, the children are moved to the new node, if the renamed node is an Element its attributes are moved to the new node, the new node is inserted at the position the old node used to have in its parent's child nodes list if it has one, the user data that was attached to the old node is attached to the new node.

When the node being renamed is an Element only the specified attributes are moved, default attributes originated from the DTD are updated according to the new element name. In addition, the implementation may update default attributes from other schemas. Applications should use Document.normalizeDocument() to guarantee these attributes are up-to-date.

When the node being renamed is an Attr that is attached to an Element, the node is first removed from the Element attributes map. Then, once renamed, either by modifying the existing node or creating a new one as described above, it is put back.

In addition,

• a user data event NODE_RENAMED is fired,

• when the implementation supports the feature "MutationNameEvents", each mutation operation involved in this method fires the appropriate event, and in the end the event {http://www.w3.org/2001/xml-events, DOMElementNameChanged} or {http://www.w3.org/2001/xml-events, DOMAttributeNameChanged} is fired.

The node to rename.

The new namespace URI.

The new qualified name.

The renamed node. This is either the specified node or the new node that was created to replace the specified node.

NOT_SUPPORTED_ERR: Raised when the type of the specified node is neither ELEMENT_NODE nor ATTRIBUTE_NODE, or if the implementation does not support the renaming of the document element.

INVALID_CHARACTER_ERR: Raised if the new qualified name is not an XML name according to the XML version in use specified in the Document.xmlVersion attribute.

WRONG_DOCUMENT_ERR: Raised when the specified node was created from a different document than this document.

NAMESPACE_ERR: Raised if the qualifiedName is a malformed qualified name, if the qualifiedName has a prefix and the namespaceURI is null, or if the qualifiedName has a prefix that is "xml" and the namespaceURI is different from "http://www.w3.org/XML/1998/namespace" [Namespaces]. Also raised, when the node being renamed is an attribute, if the qualifiedName, or its prefix, is "xmlns" and the namespaceURI is different from "http://www.w3.org/2000/xmlns/".

The Node interface is the primary datatype for the entire Document Object Model. It represents a single node in the document tree. While all objects implementing the Node interface expose methods for dealing with children, not all objects implementing the Node interface may have children. For example, Text nodes may not have children, and adding children to such nodes results in a DOMException being raised.

The attributes nodeName, nodeValue and attributes are included as a mechanism to get at node information without casting down to the specific derived interface. In cases where there is no obvious mapping of these attributes for a specific nodeType (e.g., nodeValue for an Element or attributes for a Comment), this returns null. Note that the specialized interfaces may contain additional and more convenient mechanisms to get and set the relevant information.

An integer indicating which type of node this is.

NOTE: 

Numeric codes up to 200 are reserved to W3C for possible future use.

The node is an Element.

The node is an Attr.

The node is a Text node.

The node is a CDATASection.

The node is an EntityReference.

The node is an Entity.

The node is a ProcessingInstruction.

The node is a Comment.

The node is a Document.

The node is a DocumentType.

The node is a DocumentFragment.

The node is a Notation.

The values of nodeName, nodeValue, and attributes vary according to the node type as follows: 3Layout table: the first cell contains the name of the interface, the second contains the value of the nodeName attribute for this interface, the third contains the value of the nodeValue attribute for this interface and the fourth contains the value of the attributes attribute for this interface1 Interface nodeName nodeValue attributes

11Attr	11same as Attr.name	11same as Attr.value	11null
11CDATASection	11"#cdata-section"	11same as CharacterData.data, the content of the CDATA Section	11null
11Comment	11"#comment"	11same as CharacterData.data, the content of the comment	11null
11Document	11"#document"	11null	11null
11DocumentFragment	11"#document-fragment"	11null	11null
11DocumentType	11same as DocumentType.name	11null	11null
11Element	11same as Element.tagName	11null	11NamedNodeMap
11Entity	11entity name	11null	11null
11EntityReference	11name of entity referenced	11null	11null
11Notation	11notation name	11null	11null
11ProcessingInstruction	11same as ProcessingInstruction.target	11same as ProcessingInstruction.data	11null
11Text	11"#text"	11same as CharacterData.data, the content of the text node	11null

The name of this node, depending on its type; see the table above.

The value of this node, depending on its type; see the table above. When it is defined to be null, setting it has no effect, including if the node is read-only.

NO_MODIFICATION_ALLOWED_ERR: Raised when the node is readonly and if it is not defined to be null.

DOMSTRING_SIZE_ERR: Raised when it would return more characters than fit in a DOMString variable on the implementation platform.

A code representing the type of the underlying object, as defined above.

The parent of this node. All nodes, except Attr, Document, DocumentFragment, Entity, and Notation may have a parent. However, if a node has just been created and not yet added to the tree, or if it has been removed from the tree, this is null.

A NodeList that contains all children of this node. If there are no children, this is a NodeList containing no nodes.

The first child of this node. If there is no such node, this returns null.

The last child of this node. If there is no such node, this returns null.

The node immediately preceding this node. If there is no such node, this returns null.

The node immediately following this node. If there is no such node, this returns null.

A NamedNodeMap containing the attributes of this node (if it is an Element) or null otherwise.

The Document object associated with this node. This is also the Document object used to create new nodes. When this node is a Document or a DocumentType which is not used with any Document yet, this is null.

Inserts the node newChild before the existing child node refChild. If refChild is null, insert newChild at the end of the list of children.

If newChild is a DocumentFragment object, all of its children are inserted, in the same order, before refChild. If the newChild is already in the tree, it is first removed.

NOTE: 

Inserting a node before itself is implementation dependent.

The node to insert.

The reference node, i.e., the node before which the new node must be inserted.

The node being inserted.

HIERARCHY_REQUEST_ERR: Raised if this node is of a type that does not allow children of the type of the newChild node, or if the node to insert is one of this node's ancestors or this node itself, or if this node is of type Document and the DOM application attempts to insert a second DocumentType or Element node.

WRONG_DOCUMENT_ERR: Raised if newChild was created from a different document than the one that created this node.

NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly or if the parent of the node being inserted is readonly.

NOT_FOUND_ERR: Raised if refChild is not a child of this node.

NOT_SUPPORTED_ERR: if this node is of type Document, this exception might be raised if the DOM implementation doesn't support the insertion of a DocumentType or Element node.

Replaces the child node oldChild with newChild in the list of children, and returns the oldChild node.

If newChild is a DocumentFragment object, oldChild is replaced by all of the DocumentFragment children, which are inserted in the same order. If the newChild is already in the tree, it is first removed.

NOTE: 

Replacing a node with itself is implementation dependent.

The new node to put in the child list.

The node being replaced in the list.

The node replaced.

HIERARCHY_REQUEST_ERR: Raised if this node is of a type that does not allow children of the type of the newChild node, or if the node to put in is one of this node's ancestors or this node itself, or if this node is of type Document and the result of the replacement operation would add a second DocumentType or Element on the Document node.

WRONG_DOCUMENT_ERR: Raised if newChild was created from a different document than the one that created this node.

NO_MODIFICATION_ALLOWED_ERR: Raised if this node or the parent of the new node is readonly.

NOT_FOUND_ERR: Raised if oldChild is not a child of this node.

NOT_SUPPORTED_ERR: if this node is of type Document, this exception might be raised if the DOM implementation doesn't support the replacement of the DocumentType child or Element child.

Removes the child node indicated by oldChild from the list of children, and returns it.

The node being removed.

The node removed.

NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.

NOT_FOUND_ERR: Raised if oldChild is not a child of this node.

NOT_SUPPORTED_ERR: if this node is of type Document, this exception might be raised if the DOM implementation doesn't support the removal of the DocumentType child or the Element child.

Adds the node newChild to the end of the list of children of this node. If the newChild is already in the tree, it is first removed.

The node to add.

If it is a DocumentFragment object, the entire contents of the document fragment are moved into the child list of this node

The node added.

HIERARCHY_REQUEST_ERR: Raised if this node is of a type that does not allow children of the type of the newChild node, or if the node to append is one of this node's ancestors or this node itself, or if this node is of type Document and the DOM application attempts to append a second DocumentType or Element node.

WRONG_DOCUMENT_ERR: Raised if newChild was created from a different document than the one that created this node.

NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly or if the previous parent of the node being inserted is readonly.

NOT_SUPPORTED_ERR: if the newChild node is a child of the Document node, this exception might be raised if the DOM implementation doesn't support the removal of the DocumentType child or Element child.

Returns whether this node has any children.

Returns true if this node has any children, false otherwise.

Returns a duplicate of this node, i.e., serves as a generic copy constructor for nodes. The duplicate node has no parent (parentNode is null) and no user data. User data associated to the imported node is not carried over. However, if any UserDataHandlers has been specified along with the associated data these handlers will be called with the appropriate parameters before this method returns.

Cloning an Element copies all attributes and their values, including those generated by the XML processor to represent defaulted attributes, but this method does not copy any children it contains unless it is a deep clone. This includes text contained in an the Element since the text is contained in a child Text node. Cloning an Attr directly, as opposed to be cloned as part of an Element cloning operation, returns a specified attribute (specified is true). Cloning an Attr always clones its children, since they represent its value, no matter whether this is a deep clone or not. Cloning an EntityReference automatically constructs its subtree if a corresponding Entity is available, no matter whether this is a deep clone or not. Cloning any other type of node simply returns a copy of this node.

Note that cloning an immutable subtree results in a mutable copy, but the children of an EntityReference clone are readonly. In addition, clones of unspecified Attr nodes are specified. And, cloning Document, DocumentType, Entity, and Notation nodes is implementation dependent.

If true, recursively clone the subtree under the specified node; if false, clone only the node itself (and its attributes, if it is an Element).

The duplicate node.

Puts all Text nodes in the full depth of the sub-tree underneath this Node, including attribute nodes, into a "normal" form where only structure (e.g., elements, comments, processing instructions, CDATA sections, and entity references) separates Text nodes, i.e., there are neither adjacent Text nodes nor empty Text nodes. This can be used to ensure that the DOM view of a document is the same as if it were saved and re-loaded, and is useful when operations (such as XPointer [XPointer] lookups) that depend on a particular document tree structure are to be used. If the parameter "normalize-characters" of the DOMConfiguration object attached to the Node.ownerDocument is true, this method will also fully normalize the characters of the Text nodes.

NOTE: 

In cases where the document contains CDATASections, the normalize operation alone may not be sufficient, since XPointers do not differentiate between Text nodes and CDATASection nodes.

Tests whether the DOM implementation implements a specific feature and that feature is supported by this node, as specified in [DOM Features].

The name of the feature to test.

This is the version number of the feature to test.

Returns true if the specified feature is supported on this node, false otherwise.

The namespace URI of this node, or null if it is unspecified (see [XML Namespaces]).

This is not a computed value that is the result of a namespace lookup based on an examination of the namespace declarations in scope. It is merely the namespace URI given at creation time.

For nodes of any type other than ELEMENT_NODE and ATTRIBUTE_NODE and nodes created with a DOM Level 1 method, such as Document.createElement(), this is always null.

NOTE: 

Per the Namespaces in XML Specification [Namespaces] an attribute does not inherit its namespace from the element it is attached to. If an attribute is not explicitly given a namespace, it simply has no namespace.

The namespace prefix of this node, or null if it is unspecified. When it is defined to be null, setting it has no effect, including if the node is read-only.

Note that setting this attribute, when permitted, changes the nodeName attribute, which holds the qualified name, as well as the tagName and name attributes of the Element and Attr interfaces, when applicable.

Setting the prefix to null makes it unspecified, setting it to an empty string is implementation dependent.

Note also that changing the prefix of an attribute that is known to have a default value, does not make a new attribute with the default value and the original prefix appear, since the namespaceURI and localName do not change.

For nodes of any type other than ELEMENT_NODE and ATTRIBUTE_NODE and nodes created with a DOM Level 1 method, such as createElement from the Document interface, this is always null.

INVALID_CHARACTER_ERR: Raised if the specified prefix contains an illegal character according to the XML version in use specified in the Document.xmlVersion attribute.

NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.

NAMESPACE_ERR: Raised if the specified prefix is malformed per the Namespaces in XML specification, if the namespaceURI of this node is null, if the specified prefix is "xml" and the namespaceURI of this node is different from "http://www.w3.org/XML/1998/namespace", if this node is an attribute and the specified prefix is "xmlns" and the namespaceURI of this node is different from "http://www.w3.org/2000/xmlns/", or if this node is an attribute and the qualifiedName of this node is "xmlns" [Namespaces].

Returns the local part of the qualified name of this node.

For nodes of any type other than ELEMENT_NODE and ATTRIBUTE_NODE and nodes created with a DOM Level 1 method, such as Document.createElement(), this is always null.

Returns whether this node (if it is an element) has any attributes.

Returns true if this node has any attributes, false otherwise.

The absolute base URI of this node or null if the implementation wasn't able to obtain an absolute URI. This value is computed as described in [Base URIs]. However, when the Document supports the feature "HTML" [DOM2HTML], the base URI is computed using first the value of the href attribute of the HTML BASE element if any, and the value of the documentURI attribute from the Document interface otherwise.

A bitmask indicating the relative document position of a node with respect to another node.

If the two nodes being compared are the same node, then no flags are set on the return.

Otherwise, the order of two nodes is determined by looking for common containers -- containers which contain both. A node directly contains any child nodes. A node also directly contains any other nodes attached to it such as attributes contained in an element or entities and notations contained in a document type. Nodes contained in contained nodes are also contained, but less-directly as the number of intervening containers increases.

If there is no common container node, then the order is based upon order between the root container of each node that is in no container. In this case, the result is disconnected and implementation-specific. This result is stable as long as these outer-most containing nodes remain in memory and are not inserted into some other containing node. This would be the case when the nodes belong to different documents or fragments, and cloning the document or inserting a fragment might change the order.

If one of the nodes being compared contains the other node, then the container precedes the contained node, and reversely the contained node follows the container. For example, when comparing an element against its own attribute or child, the element node precedes its attribute node and its child node, which both follow it.

If neither of the previous cases apply, then there exists a most-direct container common to both nodes being compared. In this case, the order is determined based upon the two determining nodes directly contained in this most-direct common container that either are or contain the corresponding nodes being compared.

If these two determining nodes are both child nodes, then the natural DOM order of these determining nodes within the containing node is returned as the order of the corresponding nodes. This would be the case, for example, when comparing two child elements of the same element.

If one of the two determining nodes is a child node and the other is not, then the corresponding node of the child node follows the corresponding node of the non-child node. This would be the case, for example, when comparing an attribute of an element with a child element of the same element.

If neither of the two determining node is a child node and one determining node has a greater value of nodeType than the other, then the corresponding node precedes the other. This would be the case, for example, when comparing an entity of a document type against a notation of the same document type.

If neither of the two determining node is a child node and nodeType is the same for both determining nodes, then an implementation-dependent order between the determining nodes is returned. This order is stable as long as no nodes of the same nodeType are inserted into or removed from the direct container. This would be the case, for example, when comparing two attributes of the same element, and inserting or removing additional attributes might change the order between existing attributes.

The two nodes are disconnected. Order between disconnected nodes is always implementation-specific.

The second node precedes the reference node.

The node follows the reference node.

The node contains the reference node. A node which contains is always preceding, too.

The node is contained by the reference node. A node which is contained is always following, too.

The determination of preceding versus following is implementation-specific.

Compares the reference node, i.e. the node on which this method is being called, with a node, i.e. the one passed as a parameter, with regard to their position in the document and according to the document order.

The node to compare against the reference node.

Returns how the node is positioned relatively to the reference node.

NOT_SUPPORTED_ERR: when the compared nodes are from different DOM implementations that do not coordinate to return consistent implementation-specific results.

This attribute returns the text content of this node and its descendants. When it is defined to be null, setting it has no effect. On setting, any possible children this node may have are removed and, if it the new string is not empty or null, replaced by a single Text node containing the string this attribute is set to.

On getting, no serialization is performed, the returned string does not contain any markup. No whitespace normalization is performed and the returned string does not contain the white spaces in element content (see the attribute Text.isElementContentWhitespace). Similarly, on setting, no parsing is performed either, the input string is taken as pure textual content.

The string returned is made of the text content of this node depending on its type, as defined below:

NO_MODIFICATION_ALLOWED_ERR: Raised when the node is readonly.

DOMSTRING_SIZE_ERR: Raised when it would return more characters than fit in a DOMString variable on the implementation platform.

Returns whether this node is the same node as the given one.

This method provides a way to determine whether two Node references returned by the implementation reference the same object. When two Node references are references to the same object, even if through a proxy, the references may be used completely interchangeably, such that all attributes have the same values and calling the same DOM method on either reference always has exactly the same effect.

The node to test against.

Returns true if the nodes are the same, false otherwise.

Look up the prefix associated to the given namespace URI, starting from this node. The default namespace declarations are ignored by this method.

See [Namespace Prefix Lookup] for details on the algorithm used by this method.

The namespace URI to look for.

Returns an associated namespace prefix if found or null if none is found. If more than one prefix are associated to the namespace prefix, the returned namespace prefix is implementation dependent.

This method checks if the specified namespaceURI is the default namespace or not.

The namespace URI to look for.

Returns true if the specified namespaceURI is the default namespace, false otherwise.

Look up the namespace URI associated to the given prefix, starting from this node.

See [Namespace URI Lookup] for details on the algorithm used by this method.

The prefix to look for. If this parameter is null, the method will return the default namespace URI if any.

Returns the associated namespace URI or null if none is found.

Tests whether two nodes are equal.

This method tests for equality of nodes, not sameness (i.e., whether the two nodes are references to the same object) which can be tested with Node.isSameNode(). All nodes that are the same will also be equal, though the reverse may not be true.

Two nodes are equal if and only if the following conditions are satisfied:

• The two nodes are of the same type.

• The following string attributes are equal: nodeName, localName, namespaceURI, prefix, nodeValue. This is: they are both null, or they have the same length and are character for character identical.

• The attributes NamedNodeMaps are equal. This is: they are both null, or they have the same length and for each node that exists in one map there is a node that exists in the other map and is equal, although not necessarily at the same index.

• The childNodes NodeLists are equal. This is: they are both null, or they have the same length and contain equal nodes at the same index. Note that normalization can affect equality; to avoid this, nodes should be normalized before being compared.

For two DocumentType nodes to be equal, the following conditions must also be satisfied:

• The following string attributes are equal: publicId, systemId, internalSubset.

• The entities NamedNodeMaps are equal.

• The notations NamedNodeMaps are equal.

On the other hand, the following do not affect equality: the ownerDocument, baseURI, and parentNode attributes, the specified attribute for Attr nodes, the schemaTypeInfo attribute for Attr and Element nodes, the Text.isElementContentWhitespace attribute for Text nodes, as well as any user data or event listeners registered on the nodes.

NOTE: 

As a general rule, anything not mentioned in the description above is not significant in consideration of equality checking. Note that future versions of this specification may take into account more attributes and implementations conform to this specification are expected to be updated accordingly.

The node to compare equality with.

Returns true if the nodes are equal, false otherwise.

This method returns a specialized object which implements the specialized APIs of the specified feature and version, as specified in [DOM Features]. The specialized object may also be obtained by using binding-specific casting methods but is not necessarily expected to, as discussed in [Mixed DOM Implementations]. This method also allow the implementation to provide specialized objects which do not support the Node interface.

The name of the feature requested. Note that any plus sign "+" prepended to the name of the feature will be ignored since it is not significant in the context of this method.

This is the version number of the feature to test.

Returns an object which implements the specialized APIs of the specified feature and version, if any, or null if there is no object which implements interfaces associated with that feature. If the DOMObject returned by this method implements the Node interface, it must delegate to the primary core Node and not return results inconsistent with the primary core Node such as attributes, childNodes, etc.

Associate an object to a key on this node. The object can later be retrieved from this node by calling getUserData with the same key.

The key to associate the object to.

The object to associate to the given key, or null to remove any existing association to that key.

The handler to associate to that key, or null.

Returns the DOMUserData previously associated to the given key on this node, or null if there was none.

Retrieves the object associated to a key on a this node. The object must first have been set to this node by calling setUserData with the same key.

The key the object is associated to.

Returns the DOMUserData associated to the given key on this node, or null if there was none.

The NodeList interface provides the abstraction of an ordered collection of nodes, without defining or constraining how this collection is implemented. NodeList objects in the DOM are live.

The items in the NodeList are accessible via an integral index, starting from 0.

Returns the indexth item in the collection. If index is greater than or equal to the number of nodes in the list, this returns null.

Index into the collection.

The node at the indexth position in the NodeList, or null if that is not a valid index.

The number of nodes in the list. The range of valid child node indices is 0 to length-1 inclusive.

Objects implementing the NamedNodeMap interface are used to represent collections of nodes that can be accessed by name. Note that NamedNodeMap does not inherit from NodeList; NamedNodeMaps are not maintained in any particular order. Objects contained in an object implementing NamedNodeMap may also be accessed by an ordinal index, but this is simply to allow convenient enumeration of the contents of a NamedNodeMap, and does not imply that the DOM specifies an order to these Nodes.

NamedNodeMap objects in the DOM are live.

Retrieves a node specified by name.

The nodeName of a node to retrieve.

A Node (of any type) with the specified nodeName, or null if it does not identify any node in this map.

Adds a node using its nodeName attribute. If a node with that name is already present in this map, it is replaced by the new one. Replacing a node by itself has no effect.

As the nodeName attribute is used to derive the name which the node must be stored under, multiple nodes of certain types (those that have a "special" string value) cannot be stored as the names would clash. This is seen as preferable to allowing nodes to be aliased.

A node to store in this map. The node will later be accessible using the value of its nodeName attribute.

If the new Node replaces an existing node the replaced Node is returned, otherwise null is returned.

WRONG_DOCUMENT_ERR: Raised if arg was created from a different document than the one that created this map.

NO_MODIFICATION_ALLOWED_ERR: Raised if this map is readonly.

INUSE_ATTRIBUTE_ERR: Raised if arg is an Attr that is already an attribute of another Element object. The DOM user must explicitly clone Attr nodes to re-use them in other elements.

HIERARCHY_REQUEST_ERR: Raised if an attempt is made to add a node doesn't belong in this NamedNodeMap. Examples would include trying to insert something other than an Attr node into an Element's map of attributes, or a non-Entity node into the DocumentType's map of Entities.

Removes a node specified by name. When this map contains the attributes attached to an element, if the removed attribute is known to have a default value, an attribute immediately appears containing the default value as well as the corresponding namespace URI, local name, and prefix when applicable.

The nodeName of the node to remove.

The node removed from this map if a node with such a name exists.

NOT_FOUND_ERR: Raised if there is no node named name in this map.

NO_MODIFICATION_ALLOWED_ERR: Raised if this map is readonly.

Returns the indexth item in the map. If index is greater than or equal to the number of nodes in this map, this returns null.

Index into this map.

The node at the indexth position in the map, or null if that is not a valid index.

The number of nodes in this map. The range of valid child node indices is 0 to length-1 inclusive.

Retrieves a node specified by local name and namespace URI.

Per [Namespaces], applications must use the value null as the namespaceURI parameter for methods if they wish to have no namespace.

The namespace URI of the node to retrieve.

The local name of the node to retrieve.

A Node (of any type) with the specified local name and namespace URI, or null if they do not identify any node in this map.

NOT_SUPPORTED_ERR: May be raised if the implementation does not support the feature "XML" and the language exposed through the Document does not support XML Namespaces (such as [HTML40]).

Adds a node using its namespaceURI and localName. If a node with that namespace URI and that local name is already present in this map, it is replaced by the new one. Replacing a node by itself has no effect.

Per [Namespaces], applications must use the value null as the namespaceURI parameter for methods if they wish to have no namespace.

A node to store in this map. The node will later be accessible using the value of its namespaceURI and localName attributes.

If the new Node replaces an existing node the replaced Node is returned, otherwise null is returned.

WRONG_DOCUMENT_ERR: Raised if arg was created from a different document than the one that created this map.

NO_MODIFICATION_ALLOWED_ERR: Raised if this map is readonly.

INUSE_ATTRIBUTE_ERR: Raised if arg is an Attr that is already an attribute of another Element object. The DOM user must explicitly clone Attr nodes to re-use them in other elements.

HIERARCHY_REQUEST_ERR: Raised if an attempt is made to add a node doesn't belong in this NamedNodeMap. Examples would include trying to insert something other than an Attr node into an Element's map of attributes, or a non-Entity node into the DocumentType's map of Entities.

NOT_SUPPORTED_ERR: May be raised if the implementation does not support the feature "XML" and the language exposed through the Document does not support XML Namespaces (such as [HTML40]).

Removes a node specified by local name and namespace URI. A removed attribute may be known to have a default value when this map contains the attributes attached to an element, as returned by the attributes attribute of the Node interface. If so, an attribute immediately appears containing the default value as well as the corresponding namespace URI, local name, and prefix when applicable.

Per [Namespaces], applications must use the value null as the namespaceURI parameter for methods if they wish to have no namespace.

The namespace URI of the node to remove.

The local name of the node to remove.

The node removed from this map if a node with such a local name and namespace URI exists.

NOT_FOUND_ERR: Raised if there is no node with the specified namespaceURI and localName in this map.

NO_MODIFICATION_ALLOWED_ERR: Raised if this map is readonly.

NOT_SUPPORTED_ERR: May be raised if the implementation does not support the feature "XML" and the language exposed through the Document does not support XML Namespaces (such as [HTML40]).

The CharacterData interface extends Node with a set of attributes and methods for accessing character data in the DOM. For clarity this set is defined here rather than on each object that uses these attributes and methods. No DOM objects correspond directly to CharacterData, though Text and others do inherit the interface from it. All offsets in this interface start from 0.

As explained in the DOMString interface, text strings in the DOM are represented in UTF-16, i.e. as a sequence of 16-bit units. In the following, the term 16-bit units is used whenever necessary to indicate that indexing on CharacterData is done in 16-bit units.

The character data of the node that implements this interface. The DOM implementation may not put arbitrary limits on the amount of data that may be stored in a CharacterData node. However, implementation limits may mean that the entirety of a node's data may not fit into a single DOMString. In such cases, the user may call substringData to retrieve the data in appropriately sized pieces.

NO_MODIFICATION_ALLOWED_ERR: Raised when the node is readonly.

DOMSTRING_SIZE_ERR: Raised when it would return more characters than fit in a DOMString variable on the implementation platform.

The number of 16-bit units that are available through data and the substringData method below. This may have the value zero, i.e., CharacterData nodes may be empty.

Extracts a range of data from the node.

Start offset of substring to extract.

The number of 16-bit units to extract.

The specified substring. If the sum of offset and count exceeds the length, then all 16-bit units to the end of the data are returned.

INDEX_SIZE_ERR: Raised if the specified offset is negative or greater than the number of 16-bit units in data, or if the specified count is negative.

DOMSTRING_SIZE_ERR: Raised if the specified range of text does not fit into a DOMString.

Append the string to the end of the character data of the node. Upon success, data provides access to the concatenation of data and the DOMString specified.

The DOMString to append.

NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.

Insert a string at the specified 16-bit unit offset.

The character offset at which to insert.

The DOMString to insert.

INDEX_SIZE_ERR: Raised if the specified offset is negative or greater than the number of 16-bit units in data.

NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.

Remove a range of 16-bit units from the node. Upon success, data and length reflect the change.

The offset from which to start removing.

The number of 16-bit units to delete. If the sum of offset and count exceeds length then all 16-bit units from offset to the end of the data are deleted.

INDEX_SIZE_ERR: Raised if the specified offset is negative or greater than the number of 16-bit units in data, or if the specified count is negative.

NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.

Replace the characters starting at the specified 16-bit unit offset with the specified string.

The offset from which to start replacing.

The number of 16-bit units to replace. If the sum of offset and count exceeds length, then all 16-bit units to the end of the data are replaced; (i.e., the effect is the same as a remove method call with the same range, followed by an append method invocation).

The DOMString with which the range must be replaced.

INDEX_SIZE_ERR: Raised if the specified offset is negative or greater than the number of 16-bit units in data, or if the specified count is negative.

NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.

The Attr interface represents an attribute in an Element object. Typically the allowable values for the attribute are defined in a schema associated with the document.

Attr objects inherit the Node interface, but since they are not actually child nodes of the element they describe, the DOM does not consider them part of the document tree. Thus, the Node attributes parentNode, previousSibling, and nextSibling have a null value for Attr objects. The DOM takes the view that attributes are properties of elements rather than having a separate identity from the elements they are associated with; this should make it more efficient to implement such features as default attributes associated with all elements of a given type. Furthermore, Attr nodes may not be immediate children of a DocumentFragment. However, they can be associated with Element nodes contained within a DocumentFragment. In short, users and implementors of the DOM need to be aware that Attr nodes have some things in common with other objects inheriting the Node interface, but they also are quite distinct.

The attribute's effective value is determined as follows: if this attribute has been explicitly assigned any value, that value is the attribute's effective value; otherwise, if there is a declaration for this attribute, and that declaration includes a default value, then that default value is the attribute's effective value; otherwise, the attribute does not exist on this element in the structure model until it has been explicitly added. Note that the Node.nodeValue attribute on the Attr instance can also be used to retrieve the string version of the attribute's value(s).

If the attribute was not explicitly given a value in the instance document but has a default value provided by the schema associated with the document, an attribute node will be created with specified set to false. Removing attribute nodes for which a default value is defined in the schema generates a new attribute node with the default value and specified set to false. If validation occurred while invoking Document.normalizeDocument(), attribute nodes with specified equals to false are recomputed according to the default attribute values provided by the schema. If no default value is associate with this attribute in the schema, the attribute node is discarded.

In XML, where the value of an attribute can contain entity references, the child nodes of the Attr node may be either Text or EntityReference nodes (when these are in use; see the description of EntityReference for discussion).

The DOM Core represents all attribute values as simple strings, even if the DTD or schema associated with the document declares them of some specific type such as tokenized.

The way attribute value normalization is performed by the DOM implementation depends on how much the implementation knows about the schema in use. Typically, the value and nodeValue attributes of an Attr node initially returns the normalized value given by the parser. It is also the case after Document.normalizeDocument() is called (assuming the right options have been set). But this may not be the case after mutation, independently of whether the mutation is performed by setting the string value directly or by changing the Attr child nodes. In particular, this is true when [character references] are involved, given that they are not represented in the DOM and they impact attribute value normalization. On the other hand, if the implementation knows about the schema in use when the attribute value is changed, and it is of a different type than CDATA, it may normalize it again at that time. This is especially true of specialized DOM implementations, such as SVG DOM implementations, which store attribute values in an internal form different from a string.

The following table gives some examples of the relations between the attribute value in the original document (parsed attribute), the value as exposed in the DOM, and the serialization of the value:

"x²=5"

"x²=5"

"x²=5"

"y<6"

"y<6"

"y<6"

"x=5
y=6"

"x=5
y=6"

"x=5
y=6"

"x=5
y=6"

"x=5 y=6"

"x=5 y=6"

<!ENTITY e
'...&#10;...'>
[...]>
"x=5&e;y=6"

Returns the name of this attribute. If Node.localName is different from null, this attribute is a qualified name.

True if this attribute was explicitly given a value in the instance document, false otherwise. If the application changed the value of this attribute node (even if it ends up having the same value as the default value) then it is set to true. The implementation may handle attributes with default values from other schemas similarly but applications should use Document.normalizeDocument() to guarantee this information is up-to-date.

On retrieval, the value of the attribute is returned as a string. Character and general entity references are replaced with their values. See also the method getAttribute on the Element interface.

On setting, this creates a Text node with the unparsed contents of the string, i.e. any characters that an XML processor would recognize as markup are instead treated as literal text. See also the method Element.setAttribute().

Some specialized implementations, such as some [SVG1] implementations, may do normalization automatically, even after mutation; in such case, the value on retrieval may differ from the value on setting.

NO_MODIFICATION_ALLOWED_ERR: Raised when the node is readonly.

The Element node this attribute is attached to or null if this attribute is not in use.

The type information associated with this attribute. While the type information contained in this attribute is guarantee to be correct after loading the document or invoking Document.normalizeDocument(), schemaTypeInfo may not be reliable if the node was moved.

Returns whether this attribute is known to be of type ID (i.e. to contain an identifier for its owner element) or not. When it is and its value is unique, the ownerElement of this attribute can be retrieved using the method Document.getElementById. The implementation could use several ways to determine if an attribute node is known to contain an identifier:

• If validation occurred using an XML Schema [XMLSchema1] while loading the document or while invoking Document.normalizeDocument(), the post-schema-validation infoset contributions (PSVI contributions) values are used to determine if this attribute is a schema-determined ID attribute using the schema-determined ID definition in [XPointer].

• If validation occurred using a DTD while loading the document or while invoking Document.normalizeDocument(), the infoset [type definition] value is used to determine if this attribute is a DTD-determined ID attribute using the DTD-determined ID definition in [XPointer].

• from the use of the methods Element.setIdAttribute(), Element.setIdAttributeNS(), or Element.setIdAttributeNode(), i.e. it is an user-determined ID attribute;

  NOTE: 

  XPointer framework (see section 3.2 in [XPointer]) consider the DOM user-determined ID attribute as being part of the XPointer externally-determined ID definition.

• using mechanisms that are outside the scope of this specification, it is then an externally-determined ID attribute. This includes using schema languages different from XML schema and DTD.

If validation occurred while invoking Document.normalizeDocument(), all user-determined ID attributes are reset and all attribute nodes ID information are then reevaluated in accordance to the schema used. As a consequence, if the Attr.schemaTypeInfo attribute contains an ID type, isId will always return true.

The Element interface represents an element in an HTML or XML document. Elements may have attributes associated with them; since the Element interface inherits from Node, the generic Node interface attribute attributes may be used to retrieve the set of all attributes for an element. There are methods on the Element interface to retrieve either an Attr object by name or an attribute value by name. In XML, where an attribute value may contain entity references, an Attr object should be retrieved to examine the possibly fairly complex sub-tree representing the attribute value. On the other hand, in HTML, where all attributes have simple string values, methods to directly access an attribute value can safely be used as a convenience.

NOTE: 

In DOM Level 2, the method normalize is inherited from the Node interface where it was moved.

The name of the element. If Node.localName is different from null, this attribute is a qualified name. For example, in:

          <elementExample id="demo"> 
          ... 
          </elementExample> ,
        

Retrieves an attribute value by name.

The name of the attribute to retrieve.

The Attr value as a string, or the empty string if that attribute does not have a specified or default value.

Adds a new attribute. If an attribute with that name is already present in the element, its value is changed to be that of the value parameter. This value is a simple string; it is not parsed as it is being set. So any markup (such as syntax to be recognized as an entity reference) is treated as literal text, and needs to be appropriately escaped by the implementation when it is written out. In order to assign an attribute value that contains entity references, the user must create an Attr node plus any Text and EntityReference nodes, build the appropriate subtree, and use setAttributeNode to assign it as the value of an attribute.

To set an attribute with a qualified name and namespace URI, use the setAttributeNS method.

The name of the attribute to create or alter.

Value to set in string form.

INVALID_CHARACTER_ERR: Raised if the specified name is not an XML name according to the XML version in use specified in the Document.xmlVersion attribute.

NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.

Removes an attribute by name. If a default value for the removed attribute is defined in the DTD, a new attribute immediately appears with the default value as well as the corresponding namespace URI, local name, and prefix when applicable. The implementation may handle default values from other schemas similarly but applications should use Document.normalizeDocument() to guarantee this information is up-to-date.

If no attribute with this name is found, this method has no effect.

To remove an attribute by local name and namespace URI, use the removeAttributeNS method.

The name of the attribute to remove.

NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.

Retrieves an attribute node by name.

To retrieve an attribute node by qualified name and namespace URI, use the getAttributeNodeNS method.

The name (nodeName) of the attribute to retrieve.

The Attr node with the specified name (nodeName) or null if there is no such attribute.

Adds a new attribute node. If an attribute with that name (nodeName) is already present in the element, it is replaced by the new one. Replacing an attribute node by itself has no effect.

To add a new attribute node with a qualified name and namespace URI, use the setAttributeNodeNS method.

The Attr node to add to the attribute list.

If the newAttr attribute replaces an existing attribute, the replaced Attr node is returned, otherwise null is returned.

WRONG_DOCUMENT_ERR: Raised if newAttr was created from a different document than the one that created the element.

NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.

INUSE_ATTRIBUTE_ERR: Raised if newAttr is already an attribute of another Element object. The DOM user must explicitly clone Attr nodes to re-use them in other elements.

Removes the specified attribute node. If a default value for the removed Attr node is defined in the DTD, a new node immediately appears with the default value as well as the corresponding namespace URI, local name, and prefix when applicable. The implementation may handle default values from other schemas similarly but applications should use Document.normalizeDocument() to guarantee this information is up-to-date.

The Attr node to remove from the attribute list.

The Attr node that was removed.

NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.

NOT_FOUND_ERR: Raised if oldAttr is not an attribute of the element.

Returns a NodeList of all descendant Elements with a given tag name, in document order.

The name of the tag to match on. The special value "*" matches all tags.

A list of matching Element nodes.

Retrieves an attribute value by local name and namespace URI.

Per [Namespaces], applications must use the value null as the namespaceURI parameter for methods if they wish to have no namespace.

The namespace URI of the attribute to retrieve.

The local name of the attribute to retrieve.

The Attr value as a string, or the empty string if that attribute does not have a specified or default value.

NOT_SUPPORTED_ERR: May be raised if the implementation does not support the feature "XML" and the language exposed through the Document does not support XML Namespaces (such as [HTML40]).

Adds a new attribute. If an attribute with the same local name and namespace URI is already present on the element, its prefix is changed to be the prefix part of the qualifiedName, and its value is changed to be the value parameter. This value is a simple string; it is not parsed as it is being set. So any markup (such as syntax to be recognized as an entity reference) is treated as literal text, and needs to be appropriately escaped by the implementation when it is written out. In order to assign an attribute value that contains entity references, the user must create an Attr node plus any Text and EntityReference nodes, build the appropriate subtree, and use setAttributeNodeNS or setAttributeNode to assign it as the value of an attribute.

Per [Namespaces], applications must use the value null as the namespaceURI parameter for methods if they wish to have no namespace.

The namespace URI of the attribute to create or alter.

The qualified name of the attribute to create or alter.

The value to set in string form.

INVALID_CHARACTER_ERR: Raised if the specified qualified name is not an XML name according to the XML version in use specified in the Document.xmlVersion attribute.

NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.

NAMESPACE_ERR: Raised if the qualifiedName is malformed per the Namespaces in XML specification, if the qualifiedName has a prefix and the namespaceURI is null, if the qualifiedName has a prefix that is "xml" and the namespaceURI is different from "http://www.w3.org/XML/1998/namespace", if the qualifiedName or its prefix is "xmlns" and the namespaceURI is different from "http://www.w3.org/2000/xmlns/", or if the namespaceURI is "http://www.w3.org/2000/xmlns/" and neither the qualifiedName nor its prefix is "xmlns".

NOT_SUPPORTED_ERR: May be raised if the implementation does not support the feature "XML" and the language exposed through the Document does not support XML Namespaces (such as [HTML40]).

Removes an attribute by local name and namespace URI. If a default value for the removed attribute is defined in the DTD, a new attribute immediately appears with the default value as well as the corresponding namespace URI, local name, and prefix when applicable. The implementation may handle default values from other schemas similarly but applications should use Document.normalizeDocument() to guarantee this information is up-to-date.

If no attribute with this local name and namespace URI is found, this method has no effect.

Per [Namespaces], applications must use the value null as the namespaceURI parameter for methods if they wish to have no namespace.

The namespace URI of the attribute to remove.

The local name of the attribute to remove.

NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.

NOT_SUPPORTED_ERR: May be raised if the implementation does not support the feature "XML" and the language exposed through the Document does not support XML Namespaces (such as [HTML40]).

Retrieves an Attr node by local name and namespace URI.

Per [Namespaces], applications must use the value null as the namespaceURI parameter for methods if they wish to have no namespace.

The namespace URI of the attribute to retrieve.

The local name of the attribute to retrieve.

The Attr node with the specified attribute local name and namespace URI or null if there is no such attribute.

NOT_SUPPORTED_ERR: May be raised if the implementation does not support the feature "XML" and the language exposed through the Document does not support XML Namespaces (such as [HTML40]).

Adds a new attribute. If an attribute with that local name and that namespace URI is already present in the element, it is replaced by the new one. Replacing an attribute node by itself has no effect.

Per [Namespaces], applications must use the value null as the namespaceURI parameter for methods if they wish to have no namespace.

The Attr node to add to the attribute list.

If the newAttr attribute replaces an existing attribute with the same local name and namespace URI, the replaced Attr node is returned, otherwise null is returned.

WRONG_DOCUMENT_ERR: Raised if newAttr was created from a different document than the one that created the element.

NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.

INUSE_ATTRIBUTE_ERR: Raised if newAttr is already an attribute of another Element object. The DOM user must explicitly clone Attr nodes to re-use them in other elements.

NOT_SUPPORTED_ERR: May be raised if the implementation does not support the feature "XML" and the language exposed through the Document does not support XML Namespaces (such as [HTML40]).

Returns a NodeList of all the descendant Elements with a given local name and namespace URI in document order.

The namespace URI of the elements to match on. The special value "*" matches all namespaces.

The local name of the elements to match on. The special value "*" matches all local names.

A new NodeList object containing all the matched Elements.

NOT_SUPPORTED_ERR: May be raised if the implementation does not support the feature "XML" and the language exposed through the Document does not support XML Namespaces (such as [HTML40]).

Returns true when an attribute with a given name is specified on this element or has a default value, false otherwise.

The name of the attribute to look for.

true if an attribute with the given name is specified on this element or has a default value, false otherwise.

Returns true when an attribute with a given local name and namespace URI is specified on this element or has a default value, false otherwise.

Per [Namespaces], applications must use the value null as the namespaceURI parameter for methods if they wish to have no namespace.

The namespace URI of the attribute to look for.

The local name of the attribute to look for.

true if an attribute with the given local name and namespace URI is specified or has a default value on this element, false otherwise.

NOT_SUPPORTED_ERR: May be raised if the implementation does not support the feature "XML" and the language exposed through the Document does not support XML Namespaces (such as [HTML40]).

The type information associated with this element.

If the parameter isId is true, this method declares the specified attribute to be a user-determined ID attribute. This affects the value of Attr.isId and the behavior of Document.getElementById, but does not change any schema that may be in use, in particular this does not affect the Attr.schemaTypeInfo of the specified Attr node. Use the value false for the parameter isId to undeclare an attribute for being a user-determined ID attribute.

To specify an attribute by local name and namespace URI, use the setIdAttributeNS method.

The name of the attribute.

Whether the attribute is a of type ID.

NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.

NOT_FOUND_ERR: Raised if the specified node is not an attribute of this element.

If the parameter isId is true, this method declares the specified attribute to be a user-determined ID attribute. This affects the value of Attr.isId and the behavior of Document.getElementById, but does not change any schema that may be in use, in particular this does not affect the Attr.schemaTypeInfo of the specified Attr node. Use the value false for the parameter isId to undeclare an attribute for being a user-determined ID attribute.

The namespace URI of the attribute.

The local name of the attribute.

Whether the attribute is a of type ID.

NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.

NOT_FOUND_ERR: Raised if the specified node is not an attribute of this element.

If the parameter isId is true, this method declares the specified attribute to be a user-determined ID attribute. This affects the value of Attr.isId and the behavior of Document.getElementById, but does not change any schema that may be in use, in particular this does not affect the Attr.schemaTypeInfo of the specified Attr node. Use the value false for the parameter isId to undeclare an attribute for being a user-determined ID attribute.

The attribute node.

Whether the attribute is a of type ID.

NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.

NOT_FOUND_ERR: Raised if the specified node is not an attribute of this element.

The Text interface inherits from CharacterData and represents the textual content (termed [character data] in XML) of an Element or Attr. If there is no markup inside an element's content, the text is contained in a single object implementing the Text interface that is the only child of the element. If there is markup, it is parsed into the information items (elements, comments, etc.) and Text nodes that form the list of children of the element.

When a document is first made available via the DOM, there is only one Text node for each block of text. Users may create adjacent Text nodes that represent the contents of a given element without any intervening markup, but should be aware that there is no way to represent the separations between these nodes in XML or HTML, so they will not (in general) persist between DOM editing sessions. The Node.normalize() method merges any such adjacent Text objects into a single node for each block of text.

No lexical check is done on the content of a Text node and, depending on its position in the document, some characters must be escaped during serialization using character references; e.g. the characters "<&" if the textual content is part of an element or of an attribute, the character sequence "]]>" when part of an element, the quotation mark character " or the apostrophe character ' when part of an attribute.

Breaks this node into two nodes at the specified offset, keeping both in the tree as siblings. After being split, this node will contain all the content up to the offset point. A new node of the same type, which contains all the content at and after the offset point, is returned. If the original node had a parent node, the new node is inserted as the next sibling of the original node. When the offset is equal to the length of this node, the new node has no data.

The 16-bit unit offset at which to split, starting from 0.

The new node, of the same type as this node.

INDEX_SIZE_ERR: Raised if the specified offset is negative or greater than the number of 16-bit units in data.

NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.

Returns whether this text node contains [element content whitespace], often abusively called "ignorable whitespace". The text node is determined to contain whitespace in element content during the load of the document or if validation occurs while using Document.normalizeDocument().

Returns all text of Text nodes logically-adjacent text nodes to this node, concatenated in document order.

For instance, in the example below wholeText on the Text node that contains "bar" returns "barfoo", while on the Text node that contains "foo" it returns "barfoo".

Replaces the text of the current node and all logically-adjacent text nodes with the specified text. All logically-adjacent text nodes are removed including the current node unless it was the recipient of the replacement text.

This method returns the node which received the replacement text. The returned node is:

• null, when the replacement text is the empty string;

• the current node, except when the current node is read-only;

• a new Text node of the same type (Text or CDATASection) as the current node inserted at the location of the replacement.

For instance, in the above example calling replaceWholeText on the Text node that contains "bar" with "yo" in argument results in the following:

Where the nodes to be removed are read-only descendants of an EntityReference, the EntityReference must be removed instead of the read-only nodes. If any EntityReference to be removed has descendants that are not EntityReference, Text, or CDATASection nodes, the replaceWholeText method must fail before performing any modification of the document, raising a DOMException with the code NO_MODIFICATION_ALLOWED_ERR.

For instance, in the example below calling replaceWholeText on the Text node that contains "bar" fails, because the EntityReference node "ent" contains an Element node which cannot be removed.

The content of the replacing Text node.

The Text node created with the specified content.

NO_MODIFICATION_ALLOWED_ERR: Raised if one of the Text nodes being replaced is readonly.

This interface inherits from CharacterData and represents the content of a comment, i.e., all the characters between the starting '<!--' and ending '-->'. Note that this is the definition of a comment in XML, and, in practice, HTML, although some HTML tools may implement the full SGML comment structure.

No lexical check is done on the content of a comment and it is therefore possible to have the character sequence "--" (double-hyphen) in the content, which is illegal in a comment per section 2.5 of [XML]. The presence of this character sequence must generate a fatal error during serialization.

The TypeInfo interface represents a type referenced from Element or Attr nodes, specified in the schemas associated with the document. The type is a pair of a namespace URI and name properties, and depends on the document's schema.

If the document's schema is an XML DTD [XML], the values are computed as follows:

• If this type is referenced from an Attr node, typeNamespace is "http://www.w3.org/TR/REC-xml" and typeName represents the [attribute type] property in the [InfoSet]. If there is no declaration for the attribute, typeNamespace and typeName are null.

• If this type is referenced from an Element node, typeNamespace and typeName are null.

If the document's schema is an XML Schema [XMLSchema1], the values are computed as follows using the post-schema-validation infoset contributions (also called PSVI contributions):

• If the [validity] property exists AND is "invalid" or "notKnown": the {target namespace} and {name} properties of the declared type if available, otherwise null.

  NOTE: 

  At the time of writing, the XML Schema specification does not require exposing the declared type. Thus, DOM implementations might choose not to provide type information if validity is not valid.

• If the [validity] property exists and is "valid":

  1. If [member type definition] exists:

     1. If {name} is not absent, then expose {name} and {target namespace} properties of the [member type definition] property;

     2. Otherwise, expose the namespace and local name of the corresponding anonymous type name.

  2. If the [type definition] property exists:

     1. If {name} is not absent, then expose {name} and {target namespace} properties of the [type definition] property;

     2. Otherwise, expose the namespace and local name of the corresponding anonymous type name.

  3. If the [member type definition anonymous] exists:

     1. If it is false, then expose [member type definition name] and [member type definition namespace] properties;

     2. Otherwise, expose the namespace and local name of the corresponding anonymous type name.

  4. If the [type definition anonymous] exists:

     1. If it is false, then expose [type definition name] and [type definition namespace] properties;

     2. Otherwise, expose the namespace and local name of the corresponding anonymous type name.

NOTE: 

Other schema languages are outside the scope of the W3C and therefore should define how to represent their type systems using TypeInfo.

The name of a type declared for the associated element or attribute, or null if unknown.

The namespace of the type declared for the associated element or attribute or null if the element does not have declaration or if no namespace information is available.

These are the available values for the derivationMethod parameter used by the method TypeInfo.isDerivedFrom(). It is a set of possible types of derivation, and the values represent bit positions. If a bit in the derivationMethod parameter is set to 1, the corresponding type of derivation will be taken into account when evaluating the derivation between the reference type definition and the other type definition. When using the isDerivedFrom method, combining all of them in the derivationMethod parameter is equivalent to invoking the method for each of them separately and combining the results with the OR boolean function. This specification only defines the type of derivation for XML Schema.

In addition to the types of derivation listed below, please note that:

• any type derives from xsd:anyType.

• any simple type derives from xsd:anySimpleType by restriction.

• any complex type does not derive from xsd:anySimpleType by restriction.

If the document's schema is an XML Schema [XMLSchema1], this constant represents the derivation by [restriction] if complex types are involved, or a [restriction] if simple types are involved.

The reference type definition is derived by restriction from the other type definition if the other type definition is the same as the reference type definition, or if the other type definition can be reached recursively following the {base type definition} property from the reference type definition, and all the derivation methods involved are restriction.

If the document's schema is an XML Schema [XMLSchema1], this constant represents the derivation by [extension].

The reference type definition is derived by extension from the other type definition if the other type definition can be reached recursively following the {base type definition} property from the reference type definition, and at least one of the derivation methods involved is an extension.

If the document's schema is an XML Schema [XMLSchema1], this constant represents the [union] if simple types are involved.

The reference type definition is derived by union from the other type definition if there exists two type definitions T1 and T2 such as the reference type definition is derived from T1 by DERIVATION_RESTRICTION or DERIVATION_EXTENSION, T2 is derived from the other type definition by DERIVATION_RESTRICTION, T1 has {variety} union, and one of the {member type definitions} is T2. Note that T1 could be the same as the reference type definition, and T2 could be the same as the other type definition.

If the document's schema is an XML Schema [XMLSchema1], this constant represents the [list].

The reference type definition is derived by list from the other type definition if there exists two type definitions T1 and T2 such as the reference type definition is derived from T1 by DERIVATION_RESTRICTION or DERIVATION_EXTENSION, T2 is derived from the other type definition by DERIVATION_RESTRICTION, T1 has {variety} list, and T2 is the {item type definition}. Note that T1 could be the same as the reference type definition, and T2 could be the same as the other type definition.

This method returns if there is a derivation between the reference type definition, i.e. the TypeInfo on which the method is being called, and the other type definition, i.e. the one passed as parameters.

the namespace of the other type definition.

the name of the other type definition.

the type of derivation and conditions applied between two types, as described in the list of constants provided in this interface.

If the document's schema is a DTD or no schema is associated with the document, this method will always return false.

If the document's schema is an XML Schema, the method will true if the reference type definition is derived from the other type definition according to the derivation parameter. If the value of the parameter is 0 (no bit is set to 1 for the derivationMethod parameter), the method will return true if the other type definition can be reached by recursing any combination of {base type definition}, {item type definition}, or {member type definitions} from the reference type definition.

When associating an object to a key on a node using Node.setUserData() the application can provide a handler that gets called when the node the object is associated to is being cloned, imported, or renamed. This can be used by the application to implement various behaviors regarding the data it associates to the DOM nodes. This interface defines that handler.

An integer indicating the type of operation being performed on a node.

The node is cloned, using Node.cloneNode().

The node is imported, using Document.importNode().

The node is deleted.

NOTE: 

This may not be supported or may not be reliable in certain environments, such as Java, where the implementation has no real control over when objects are actually deleted.

The node is renamed, using Document.renameNode().

The node is adopted, using Document.adoptNode().

This method is called whenever the node for which this handler is registered is imported or cloned.

DOM applications must not raise exceptions in a UserDataHandler. The effect of throwing exceptions from the handler is DOM implementation dependent.

Specifies the type of operation that is being performed on the node.

Specifies the key for which this handler is being called.

Specifies the data for which this handler is being called.

Specifies the node being cloned, adopted, imported, or renamed. This is null when the node is being deleted.

Specifies the node newly created if any, or null.

DOMError is an interface that describes an error.

An integer indicating the severity of the error.

The severity of the error described by the DOMError is warning. A SEVERITY_WARNING will not cause the processing to stop, unless DOMErrorHandler.handleError() returns false.

The severity of the error described by the DOMError is error. A SEVERITY_ERROR may not cause the processing to stop if the error can be recovered, unless DOMErrorHandler.handleError() returns false.

The severity of the error described by the DOMError is fatal error. A SEVERITY_FATAL_ERROR will cause the normal processing to stop. The return value of DOMErrorHandler.handleError() is ignored unless the implementation chooses to continue, in which case the behavior becomes undefined.

The severity of the error, either SEVERITY_WARNING, SEVERITY_ERROR, or SEVERITY_FATAL_ERROR.

An implementation specific string describing the error that occurred.

A DOMString indicating which related data is expected in relatedData. Users should refer to the specification of the error in order to find its DOMString type and relatedData definitions if any.

NOTE: 

As an example, Document.normalizeDocument() does generate warnings when the "split-cdata-sections" parameter is in use. Therefore, the method generates a SEVERITY_WARNING with type "cdata-sections-splitted" and the first CDATASection node in document order resulting from the split is returned by the relatedData attribute.

The related platform dependent exception if any.

The related DOMError.type dependent data if any.

The location of the error.

DOMErrorHandler is a callback interface that the DOM implementation can call when reporting errors that happens while processing XML data, or when doing some other processing (e.g. validating a document). A DOMErrorHandler object can be attached to a Document using the "error-handler" on the DOMConfiguration interface. If more than one error needs to be reported during an operation, the sequence and numbers of the errors passed to the error handler are implementation dependent.

The application that is using the DOM implementation is expected to implement this interface.

This method is called on the error handler when an error occurs.

If an exception is thrown from this method, it is considered to be equivalent of returning true.

The error object that describes the error. This object may be reused by the DOM implementation across multiple calls to the handleError method.

If the handleError method returns false, the DOM implementation should stop the current processing when possible. If the method returns true, the processing may continue depending on DOMError.severity.

DOMLocator is an interface that describes a location (e.g. where an error occurred).

The line number this locator is pointing to, or -1 if there is no column number available.

The column number this locator is pointing to, or -1 if there is no column number available.

The byte offset into the input source this locator is pointing to or -1 if there is no byte offset available.

The UTF-16, as defined in [Unicode] and Amendment 1 of [ISO10646], offset into the input source this locator is pointing to or -1 if there is no UTF-16 offset available.

The node this locator is pointing to, or null if no node is available.

The URI this locator is pointing to, or null if no URI is available.

The DOMConfiguration interface represents the configuration of a document and maintains a table of recognized parameters. Using the configuration, it is possible to change Document.normalizeDocument() behavior, such as replacing the CDATASection nodes with Text nodes or specifying the type of the schema that must be used when the validation of the Document is requested. DOMConfiguration objects are also used in [DOMLS] in the DOMParser and DOMSerializer interfaces.

The parameter names used by the DOMConfiguration object are defined throughout the DOM Level 3 specifications. Names are case-insensitive. To avoid possible conflicts, as a convention, names referring to parameters defined outside the DOM specification should be made unique. Because parameters are exposed as properties in the [ECMAScript Language Binding], names are recommended to follow the section "5.16 Identifiers" of [Unicode] with the addition of the character '-' (HYPHEN-MINUS) but it is not enforced by the DOM implementation. DOM Level 3 Core Implementations are required to recognize all parameters defined in this specification. Some parameter values may also be required to be supported by the implementation. Refer to the definition of the parameter to know if a value must be supported or not.

NOTE: 

Parameters are similar to features and properties used in SAX2 [SAX].

The following list of parameters defined in the DOM:

"canonical-form"

true

[optional]

Canonicalize the document according to the rules specified in [c14n], such as removing the DocumentType node (if any) from the tree, or removing superfluous namespace declarations from each element. Note that this is limited to what can be represented in the DOM; in particular, there is no way to specify the order of the attributes in the DOM. In addition,

Setting this parameter to true will also set the state of the parameters listed below. Later changes to the state of one of those parameters will revert "canonical-form" back to false.

Parameters set to false: "entities", "normalize-characters", "cdata-sections".

Parameters set to true: "namespaces", "namespace-declarations", "well-formed", "element-content-whitespace".

Other parameters are not changed unless explicitly specified in the description of the parameters.

false

[required] (default)

Do not canonicalize the document.

"cdata-sections"

true

[required] (default)

Keep CDATASection nodes in the document.

false

[required]

Transform CDATASection nodes in the document into Text nodes. The new Text node is then combined with any adjacent Text node.

"check-character-normalization"

true

[optional]

Check if the characters in the document are fully normalized, as defined in appendix B of [XML11]. When a sequence of characters is encountered that fails normalization checking, an error with the DOMError.type equals to "check-character-normalization-failure" is issued.

false

[required] (default)

Do not check if characters are normalized.

"comments"

true

[required] (default)

Keep Comment nodes in the document.

false

[required]

Discard Comment nodes in the document.

"datatype-normalization"

true

[optional]

Expose schema normalized values in the tree, such as XML Schema normalized values in the case of XML Schema. Since this parameter requires to have schema information, the "validate" parameter will also be set to true. Having this parameter activated when "validate" is false has no effect and no schema-normalization will happen.

NOTE: 

Since the document contains the result of the XML 1.0 processing, this parameter does not apply to attribute value normalization as defined in section 3.3.3 of [XML] and is only meant for schema languages other than Document Type Definition (DTD).

NOTE: 

For XML Schema, the

false

[required] (default)

Do not perform schema normalization on the tree.

"element-content-whitespace"

true

[required] (default)

Keep all whitespaces in the document.

false

[optional]

Discard all Text nodes that contain whitespaces in element content, as described in [[element content whitespace]]. The implementation is expected to use the attribute Text.isElementContentWhitespace to determine if a Text node should be discarded or not.

"entities"

true

[required] (default)

Keep EntityReference nodes in the document.

false

[required]

Remove all EntityReference nodes from the document, putting the entity expansions directly in their place. Text nodes are normalized, as defined in Node.normalize. Only unexpanded entity references are kept in the document.

NOTE: 

This parameter does not affect Entity nodes.

"error-handler"

[required]

Contains a DOMErrorHandler object. If an error is encountered in the document, the implementation will call back the DOMErrorHandler registered using this parameter. The implementation may provide a default DOMErrorHandler object.

When called, DOMError.relatedData will contain the closest node to where the error occurred. If the implementation is unable to determine the node where the error occurs, DOMError.relatedData will contain the Document node. Mutations to the document from within an error handler will result in implementation dependent behavior.

"infoset"

true

[required]

Keep in the document the information defined in the XML Information Set [InfoSet].

This forces the following parameters to false: "validate-if-schema", "entities", "datatype-normalization", "cdata-sections".

This forces the following parameters to true: "namespace-declarations", "well-formed", "element-content-whitespace", "comments", "namespaces".

Other parameters are not changed unless explicitly specified in the description of the parameters.

Note that querying this parameter with getParameter returns true only if the individual parameters specified above are appropriately set.

false

Setting infoset to false has no effect.

"namespaces"

true

[required] (default)

Perform the namespace processing as defined in [Namespace Normalization].

false

[optional]

Do not perform the namespace processing.

"namespace-declarations"

This parameter has no effect if the parameter "namespaces" is set to false.

true

[required] (default)

Include namespace declaration attributes, specified or defaulted from the schema, in the document. See also the sections "Declaring Namespaces" in [Namespaces] and [Namespaces11].

false

[required]

Discard all namespace declaration attributes. The namespace prefixes (Node.prefix) are retained even if this parameter is set to false.

"normalize-characters"

true

[optional]

Fully normalized the characters in the document as defined in appendix B of [XML11].

false

[required] (default)

Do not perform character normalization.

"schema-location"

[optional]

Represent a DOMString object containing a list of URIs, separated by whitespaces (characters matching the [nonterminal production S] defined in section 2.3 [XML]), that represents the schemas against which validation should occur, i.e. the current schema. The types of schemas referenced in this list must match the type specified with schema-type, otherwise the behavior of an implementation is undefined.

The schemas specified using this property take precedence to the schema information specified in the document itself. For namespace aware schema, if a schema specified using this property and a schema specified in the document instance (i.e. using the schemaLocation attribute) in a schema document (i.e. using schema import mechanisms) share the same targetNamespace, the schema specified by the user using this property will be used. If two schemas specified using this property share the same targetNamespace or have no namespace, the behavior is implementation dependent.

If no location has been provided, this parameter is null.

NOTE: 

The "schema-location" parameter is ignored unless the "schema-type" parameter value is set. It is strongly recommended that Document.documentURI will be set so that an implementation can successfully resolve any external entities referenced.

"schema-type"

[optional]

Represent a DOMString object containing an absolute URI and representing the type of the schema language used to validate a document against. Note that no lexical checking is done on the absolute URI.

If this parameter is not set, a default value may be provided by the implementation, based on the schema languages supported and on the schema language used at load time. If no value is provided, this parameter is null.

NOTE: 

For XML Schema [XMLSchema1], applications must use the value "http://www.w3.org/2001/XMLSchema". For XML DTD [XML], applications must use the value "http://www.w3.org/TR/REC-xml". Other schema languages are outside the scope of the W3C and therefore should recommend an absolute URI in order to use this method.

"split-cdata-sections"

true

[required] (default)

Split CDATA sections containing the CDATA section termination marker ']]>'. When a CDATA section is split a warning is issued with a DOMError.type equals to "cdata-sections-splitted" and DOMError.relatedData equals to the first CDATASection node in document order resulting from the split.

false

[required]

Signal an error if a CDATASection contains an unrepresentable character.

"validate"

true

[optional]

Require the validation against a schema (i.e. XML schema, DTD, any other type or representation of schema) of the document as it is being normalized as defined by [XML]. If validation errors are found, or no schema was found, the error handler is notified. Schema-normalized values will not be exposed according to the schema in used unless the parameter "datatype-normalization" is true.

This parameter will reevaluate:

• Attribute nodes with Attr.specified equals to false, as specified in the description of the Attr interface;

• The value of the attribute Text.isElementContentWhitespace for all Text nodes;

• The value of the attribute Attr.isId for all Attr nodes;

• The attributes Element.schemaTypeInfo and Attr.schemaTypeInfo.

NOTE: 

"validate-if-schema" and "validate" are mutually exclusive, setting one of them to true will set the other one to false. Applications should also consider setting the parameter "well-formed" to true, which is the default for that option, when validating the document.

false

[required] (default)

Do not accomplish schema processing, including the internal subset processing. Default attribute values information are kept. Note that validation might still happen if "validate-if-schema" is true.

"validate-if-schema"

true

[optional]

Enable validation only if a declaration for the document element can be found in a schema (independently of where it is found, i.e. XML schema, DTD, or any other type or representation of schema). If validation is enabled, this parameter has the same behavior as the parameter "validate" set to true.

NOTE: 

"validate-if-schema" and "validate" are mutually exclusive, setting one of them to true will set the other one to false.

false

[required] (default)

No schema processing should be performed if the document has a schema, including internal subset processing. Default attribute values information are kept. Note that validation must still happen if "validate" is true.

"well-formed"

true

[required] (default)

Check if all nodes are XML well formed according to the XML version in use in Document.xmlVersion:

• check if the attribute Node.nodeName contains invalid characters according to its node type and generate a DOMError of type "wf-invalid-character-in-node-name", with a DOMError.SEVERITY_ERROR severity, if necessary;

• check if the text content inside Attr, Element, Comment, Text, CDATASection nodes for invalid characters and generate a DOMError of type "wf-invalid-character", with a DOMError.SEVERITY_ERROR severity, if necessary;

• check if the data inside ProcessingInstruction nodes for invalid characters and generate a DOMError of type "wf-invalid-character", with a DOMError.SEVERITY_ERROR severity, if necessary;

false

[optional]

Do not check for XML well-formedness.

The resolution of the system identifiers associated with entities is done using Document.documentURI. However, when the feature "LS" defined in [DOMLS] is supported by the DOM implementation, the parameter "resource-resolver" can also be used on DOMConfiguration objects attached to Document nodes. If this parameter is set, Document.normalizeDocument() will invoke the resource resolver instead of using Document.documentURI.

Set the value of a parameter.

The name of the parameter to set.

The new value or null if the user wishes to unset the parameter. While the type of the value parameter is defined as DOMUserData, the object type must match the type defined by the definition of the parameter. For example, if the parameter is "error-handler", the value must be of type DOMErrorHandler.

NOT_FOUND_ERR: Raised when the parameter name is not recognized.

NOT_SUPPORTED_ERR: Raised when the parameter name is recognized but the requested value cannot be set.

TYPE_MISMATCH_ERR: Raised if the value type for this parameter name is incompatible with the expected value type.

Return the value of a parameter if known.

The name of the parameter.

The current object associated with the specified parameter or null if no object has been associated or if the parameter is not supported.

NOT_FOUND_ERR: Raised when the parameter name is not recognized.

Check if setting a parameter to a specific value is supported.

The name of the parameter to check.

An object. if null, the returned value is true.

true if the parameter could be successfully set to the specified value, or false if the parameter is not recognized or the requested value is not supported. This does not change the current value of the parameter itself.

The list of the parameters supported by this DOMConfiguration object and for which at least one value can be set by the application. Note that this list can also contain parameter names defined outside this specification.