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 usingNodeList.

Implementations should raise other exceptions under other circumstances. For example, implementations should raise an implementation-dependent exception if anullargument is passed whennullwas 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.

unsigned short

An integer indicating the type of error generated.

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 aDOMString.

If anyNodeis inserted somewhere it doesn't belong.

If aNodeis 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 aNodewhich 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 aNodein 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 asinsertBeforeorremoveChildwould make theNodeinvalid with respect to"partial validity", this exception would be raised and the operation would not be done. This code is used in. 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.

TheDOMStringListinterface provides the abstraction of an ordered collection ofDOMStringvalues, without defining or constraining how this collection is implemented. The items in theDOMStringListare accessible via an integral index, starting from 0.

Returns theindexth item in the collection. Ifindexis greater than or equal to the number ofDOMStrings in the list, this returnsnull.

Index into the collection.

TheDOMStringat theindexth position in theDOMStringList, ornullif that is not a valid index.

The number ofDOMStrings in the list. The range of valid child node indices is 0 tolength-1inclusive.

Test if a string is part of thisDOMStringList.

The string to look for.

trueif the string has been found,falseotherwise.

TheNameListinterface 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 theNameListare accessible via an integral index, starting from 0.

Returns theindexth name item in the collection.

Index into the collection.

The name at theindexth position in theNameList, ornullif there is no name for the specified index or if the index is out of range.

Returns theindexth namespaceURI item in the collection.

Index into the collection.

The namespace URI at theindexth position in theNameList, ornullif 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 tolength-1inclusive.

Test if a name is part of thisNameList.

The name to look for.

trueif the name has been found,falseotherwise.

Test if the pair namespaceURI/name is part of thisNameList.

The namespace URI to look for.

The name to look for.

trueif the pair namespaceURI/name has been found,falseotherwise.

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

Returns theindexth item in the collection. Ifindexis greater than or equal to the number ofDOMImplementations in the list, this returnsnull.

Index into the collection.

TheDOMImplementationat theindexth position in theDOMImplementationList, ornullif that is not a valid index.

The number ofDOMImplementations in the list. The range of valid child node indices is 0 tolength-1inclusive.

This interface permits a DOM implementer to supply one or more implementations, based upon requested features and versions, as specified in. Each implementedDOMImplementationSourceobject is listed in the binding-specific list of available sources so that itsDOMImplementationobjects 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 bygetDOMImplementationList.

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 methodNode.getFeature()andDOMImplementation.getFeature().

The first DOM implementation that support the desired features, ornullif this source has none.

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

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.

TheDOMImplementationinterface 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.

The name of the feature to test.

This is the version number of the feature to test.

trueif the feature is implemented in the specified version,falseotherwise.

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

Thequalified nameof the document type to be created.

The external subset public identifier.

The external subset system identifier.

A newDocumentTypenode withNode.ownerDocumentset tonull.

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

NAMESPACE_ERR: Raised if thequalifiedNameis 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).

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

Note that based on theDocumentTypegiven to create the document, the implementation may instantiate specializedDocumentobjects that support additional features than the "Core", such as "HTML". On the other hand, setting theDocumentTypeafter the document was created makes this very unlikely to happen. Alternatively, specializedDocumentcreation methods, such ascreateHTMLDocument, can be used to obtain specific types ofDocumentobjects.

Thenamespace URIof the document element to create ornull.

Thequalified nameof the document element to be created ornull.

The type of document to be created ornull.

Whendoctypeis notnull, itsNode.ownerDocumentattribute is set to the document being created.

A newDocumentobject with its document element. If theNamespaceURI,qualifiedName, anddoctypearenull, the returnedDocumentis empty with no document element.

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

NAMESPACE_ERR: Raised if thequalifiedNameis malformed, if thequalifiedNamehas a prefix and thenamespaceURIisnull, or if thequalifiedNameisnulland thenamespaceURIis different fromnull, or if thequalifiedNamehas a prefix that is "xml" and thenamespaceURIis different from "http://www.w3.org/XML/1998/namespace", 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 ifdoctypehas 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).

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

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, ornullif there is no object which implements interfaces associated with that feature. If theDOMObjectreturned by this method implements theDOMImplementationinterface, it must delegate to the primary coreDOMImplementationand not return results inconsistent with the primary coreDOMImplementationsuch ashasFeature,getFeature, etc.

DocumentFragmentis a "lightweight" or "minimal"Documentobject. 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 aDocumentobject could fulfill this role, aDocumentobject can potentially be a heavyweight object, depending on the underlying implementation. What is really needed for this is a very lightweight object.DocumentFragmentis such an object.

Furthermore, various operations -- such as inserting nodes as children of anotherNode-- may takeDocumentFragmentobjects as arguments; this results in all the child nodes of theDocumentFragmentbeing moved to the child list of this node.

The children of aDocumentFragmentnode are zero or more nodes representing the tops of any sub-trees defining the structure of the document.DocumentFragmentnodes do not need to bewell-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, aDocumentFragmentmight have only one child and that child node could be aTextnode. Such a structure model represents neither an HTML document nor a well-formed XML document.

When aDocumentFragmentis inserted into aDocument(or indeed any otherNodethat may take children) the children of theDocumentFragmentand not theDocumentFragmentitself are inserted into theNode. This makes theDocumentFragmentvery useful when the user wishes to create nodes that aresiblings; theDocumentFragmentacts as the parent of these nodes so that the user can use the standard methods from theNodeinterface, such asNode.insertBeforeandNode.appendChild.

TheDocumentinterface represents the entire HTML or XML document. Conceptually, it is therootof 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 aDocument, theDocumentinterface also contains the factory methods needed to create these objects. TheNodeobjects created have aownerDocumentattribute which associates them with theDocumentwithin whose context they were created.

The Document Type Declaration (seeDocumentType) associated with this document. For XML documents without a document type declaration this returnsnull. For HTML documents, aDocumentTypeobject may be returned, independently of the presence or absence of document type declaration in the HTML document.

This provides direct access to theDocumentTypenode, child node of thisDocument. This node can be set at document creation time and later changed through the use of child nodes manipulation methods, such asNode.insertBefore, orNode.replaceChild. Note, however, that while some implementations may instantiate different types ofDocumentobjects supporting additional features than the "Core", such as "HTML", based on theDocumentTypespecified at creation time, changing it afterwards is very unlikely to result in a change of the features supported.

TheDOMImplementationobject that handles this document. A DOM application may use objects from multiple implementations.

This is aconvenienceattribute that allows direct access to the child node that is thedocument elementof the document.

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

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

To create an element with aqualified nameandnamespace URI, use thecreateElementNSmethod.

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 newElementobject with thenodeNameattribute set totagName, andlocalName,prefix, andnamespaceURIset tonull.

INVALID_CHARACTER_ERR: Raised if the specified name is not an XML name according to the XML version in use specified in theDocument.xmlVersionattribute.

Creates an emptyDocumentFragmentobject.

A newDocumentFragment.

Creates aTextnode given the specified string.

The data for the node.

The newTextobject.

Creates aCommentnode given the specified string.

The data for the node.

The newCommentobject.

Creates aCDATASectionnode whose value is the specified string.

The data for theCDATASectioncontents.

The newCDATASectionobject.

NOT_SUPPORTED_ERR: Raised if this document is an HTML document.

Creates aProcessingInstructionnode given the specified name and data strings.

The target part of the processing instruction.

UnlikeDocument.createElementNSorDocument.createAttributeNS, no namespace well-formed checking is done on the target name. Applications should invokeDocument.normalizeDocument()with the parameter "namespaces" set totruein order to ensure that the target name is namespace well-formed.

The data for the node.

The newProcessingInstructionobject.

INVALID_CHARACTER_ERR: Raised if the specified target is not an XML name according to the XML version in use specified in theDocument.xmlVersionattribute.

NOT_SUPPORTED_ERR: Raised if this document is an HTML document.

Creates anAttrof the given name. Note that theAttrinstance can then be set on anElementusing thesetAttributeNodemethod.

To create an attribute with aqualified nameandnamespace URI, use thecreateAttributeNSmethod.

The name of the attribute.

A newAttrobject with thenodeNameattribute set toname, andlocalName,prefix, andnamespaceURIset tonull. 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 theDocument.xmlVersionattribute.

Creates anEntityReferenceobject. In addition, if the referenced entity is known, the child list of theEntityReferencenode is made the same as that of the correspondingEntitynode.

If any descendant of theEntitynode has an unboundnamespace prefix, the corresponding descendant of the createdEntityReferencenode is also unbound; (itsnamespaceURIisnull). 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.

UnlikeDocument.createElementNSorDocument.createAttributeNS, no namespace well-formed checking is done on the entity name. Applications should invokeDocument.normalizeDocument()with the parameter "namespaces" set totruein order to ensure that the entity name is namespace well-formed.

The newEntityReferenceobject.

INVALID_CHARACTER_ERR: Raised if the specified name is not an XML name according to the XML version in use specified in theDocument.xmlVersionattribute.

NOT_SUPPORTED_ERR: Raised if this document is an HTML document.

Returns aNodeListof all theElementsindocument orderwith 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, thetagnameparameter is case-sensitive, otherwise it depends on the case-sensitivity of the markup language in use.

A newNodeListobject containing all the matchedElements.

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; (parentNodeisnull).

For all nodes, importing a node creates a node object owned by the importing document, with attribute values identical to the source node'snodeNameandnodeType, plus the attributes related to namespaces (prefix,localName, andnamespaceURI). As in thecloneNodeoperation, the source node is not altered. User data associated to the imported node is not carried over. However, if anyUserDataHandlershas 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 thenodeType, 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.

TheownerElementattribute is set tonulland thespecifiedflag is set totrueon the generatedAttr. Thedescendantsof the sourceAttrare recursively imported and the resulting nodes reassembled to form the corresponding subtree.

Note that thedeepparameter has no effect onAttrnodes; they always carry their children with them when imported.

If thedeepoption was set totrue, thedescendantsof the sourceDocumentFragmentare recursively imported and the resulting nodes reassembled under the importedDocumentFragmentto form the corresponding subtree. Otherwise, this simply generates an emptyDocumentFragment.

Documentnodes cannot be imported.

DocumentTypenodes cannot be imported.

Specifiedattribute nodes of the source element are imported, and the generatedAttrnodes are attached to the generatedElement. Default attributes arenotcopied, though if the document being imported into defines default attributes for this element name, those are assigned. If theimportNodedeepparameter was set totrue, thedescendantsof the source element are recursively imported and the resulting nodes reassembled to form the corresponding subtree.

Entitynodes can be imported, however in the current release of the DOM theDocumentTypeis readonly. Ability to add these imported nodes to aDocumentTypewill be considered for addition to a future release of the DOM.

On import, thepublicId,systemId, andnotationNameattributes are copied. If adeepimport is requested, thedescendantsof the the sourceEntityare recursively imported and the resulting nodes reassembled to form the corresponding subtree.

Only theEntityReferenceitself is copied, even if adeepimport 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.

Notationnodes can be imported, however in the current release of the DOM theDocumentTypeis readonly. Ability to add these imported nodes to aDocumentTypewill be considered for addition to a future release of the DOM.

On import, thepublicIdandsystemIdattributes are copied.

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

The imported node copies itstargetanddatavalues from those of the source node.

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

These three types of nodes inheriting fromCharacterDatacopy theirdataandlengthattributes from those of the source node.

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

The node to import.

Iftrue, recursively import the subtree under the specified node; iffalse, import only the node itself, as explained above. This has no effect on nodes that cannot have any children, and onAttr, andEntityReferencenodes.

The imported node that belongs to thisDocument.

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 theDocument.xmlVersionattribute. This may happen when importing an XML 1.1element into an XML 1.0 document, for instance.

Creates an element of the givenqualified nameandnamespace URI.

Per, applications must use the valuenullas the namespaceURI parameter for methods if they wish to have no namespace.

Thenamespace URIof the element to create.

Thequalified nameof the element type to instantiate.

A newElementobject with the following attributes:

AttributeValue
Node.nodeNamequalifiedName
Node.namespaceURInamespaceURI
Node.prefixprefix, extracted fromqualifiedName, ornullif there is no prefix
Node.localNamelocal name, extracted fromqualifiedName
Element.tagNamequalifiedName

INVALID_CHARACTER_ERR: Raised if the specifiedqualifiedNameis not an XML name according to the XML version in use specified in theDocument.xmlVersionattribute.

NAMESPACE_ERR: Raised if thequalifiedNameis a malformedqualified name, if thequalifiedNamehas a prefix and thenamespaceURIisnull, or if thequalifiedNamehas a prefix that is "xml" and thenamespaceURIis different from "http://www.w3.org/XML/1998/namespace", or if thequalifiedNameor its prefix is "xmlns" and thenamespaceURIis different from "http://www.w3.org/2000/xmlns/", or if thenamespaceURIis "http://www.w3.org/2000/xmlns/" and neither thequalifiedNamenor 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 givenqualified nameandnamespace URI.

Per, applications must use the valuenullas thenamespaceURIparameter for methods if they wish to have no namespace.

Thenamespace URIof the attribute to create.

Thequalified nameof the attribute to instantiate.

A newAttrobject with the following attributes:

AttributeValue
Node.nodeNamequalifiedName
Node.namespaceURInamespaceURI
Node.prefixprefix, extracted fromqualifiedName, ornullif there is no prefix
Node.localNamelocal name, extracted fromqualifiedName
Attr.namequalifiedName
Node.nodeValuethe empty string

INVALID_CHARACTER_ERR: Raised if the specifiedqualifiedNameis not an XML name according to the XML version in use specified in theDocument.xmlVersionattribute.

NAMESPACE_ERR: Raised if thequalifiedNameis a malformedqualified name, if thequalifiedNamehas a prefix and thenamespaceURIisnull, if thequalifiedNamehas a prefix that is "xml" and thenamespaceURIis different from "http://www.w3.org/XML/1998/namespace", if thequalifiedNameor its prefix is "xmlns" and thenamespaceURIis different from "http://www.w3.org/2000/xmlns/", or if thenamespaceURIis "http://www.w3.org/2000/xmlns/" and neither thequalifiedNamenor 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 aNodeListof all theElementswith a givenlocal nameandnamespace URIindocument order.

Thenamespace URIof the elements to match on. The special value"*"matches all namespaces.

Thelocal nameof the elements to match on. The special value "*" matches all local names.

A newNodeListobject containing all the matchedElements.

Returns theElementthat has an ID attribute with the given value. If no such element exists, this returnsnull. 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 attributeAttr.isIdto determine if an attribute is of type ID.

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

The uniqueidvalue for an element.

The matching element ornullif there is none.

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

An attribute specifying, as part of theXML declaration, the encoding of this document. This isnullwhen unspecified or when it is not known, such as when theDocumentwas created in memory.

An attribute specifying, as part of theXML declaration, whether this document is standalone. This isfalsewhen unspecified.

No verification is done on the value when setting this attribute. Applications should useDocument.normalizeDocument()with the "validate" parameter to verify if the value matches thevalidity constraint for standalone document declarationas defined in.

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

An attribute specifying, as part of theXML 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 alwaysnull. Changing this attribute will affect methods that check for invalid characters in XML names. Application should invokeDocument.normalizeDocument()in order to check for invalid characters in theNodes that are already part of thisDocument.

DOM applications may use theDOMImplementation.hasFeature(feature, version)method with parameter values "XMLVersion" and "1.0" (respectively) to determine if an implementation supports. DOM applications may use the same method with parameter values "XMLVersion" and "1.1" (respectively) to determine if an implementation supports. In both cases, in order to support XML, an implementation must also support the "XML" feature defined in this specification.Documentobjects supporting a version of the "XMLVersion" feature must not raise aNOT_SUPPORTED_ERRexception for the same version number when usingDocument.xmlVersion.

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

An attribute specifying whether error checking is enforced or not. When set tofalse, the implementation is free to not test every possible error case normally defined on DOM operations, and not raise anyDOMExceptionon DOM operations or report errors while usingDocument.normalizeDocument(). In case of error, the behavior is undefined. This attribute istrueby default.

The location of the document ornullif undefined or if theDocumentwas created usingDOMImplementation.createDocument. No lexical checking is performed when setting this attribute; this could result in anullvalue returned when usingNode.baseURI.

Beware that when theDocumentsupports the feature "HTML", the href attribute of the HTML BASE element takes precedence over this attribute when computingNode.baseURI.

Attempts to adopt a node from another document to this document. If supported, it changes theownerDocumentof 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 (unlikeimportNode()which create a copy of the source node instead of moving it). When it fails, applications should useDocument.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.

TheownerElementattribute is set tonulland thespecifiedflag is set totrueon the adoptedAttr. The descendants of the sourceAttrare recursively adopted.

The descendants of the source node are recursively adopted.

Documentnodes cannot be adopted.

DocumentTypenodes cannot be adopted.

Specifiedattribute 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.

Entitynodes cannot be adopted.

Only theEntityReferencenode 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.

Notationnodes cannot be adopted.

These nodes can all be adopted. No specifics.

Since it does not create new nodes unlike theDocument.importNode()method, this method does not raise anINVALID_CHARACTER_ERRexception, and applications should use theDocument.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, ornullif this operation fails, such as when the source node comes from a different implementation.

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

NO_MODIFICATION_ALLOWED_ERR: Raised when the source node is readonly.

The configuration used whenDocument.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 ofEntityReferencenodes and normalizesTextnodes, as defined in the methodNode.normalize().

Otherwise, the actual result depends on the features being set on theDocument.domConfigobject and governing what operations actually take place. Noticeably this method could also make the documentnamespace well-formedaccording to the algorithm described in, check the character normalization, remove theCDATASectionnodes, etc. SeeDOMConfigurationfor 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 aread-only nodeor aNode.nodeNamecontains an invalid character according to the XML version in use, errors or warnings (DOMError.SEVERITY_ERRORorDOMError.SEVERITY_WARNING) will be reported using theDOMErrorHandlerobject 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 typeELEMENT_NODEorATTRIBUTE_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 anElementits 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 anElementonly 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 useDocument.normalizeDocument()to guarantee these attributes are up-to-date.

When the node being renamed is anAttrthat is attached to anElement, the node is first removed from theElementattributes 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 eventNODE_RENAMEDis 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 newnamespace URI.

The newqualified 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 neitherELEMENT_NODEnorATTRIBUTE_NODE, or if the implementation does not support the renaming of thedocument element.

INVALID_CHARACTER_ERR: Raised if the new qualified name is not an XML name according to the XML version in use specified in theDocument.xmlVersionattribute.

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

NAMESPACE_ERR: Raised if thequalifiedNameis a malformedqualified name, if thequalifiedNamehas a prefix and thenamespaceURIisnull, or if thequalifiedNamehas a prefix that is "xml" and thenamespaceURIis different from "http://www.w3.org/XML/1998/namespace". Also raised, when the node being renamed is an attribute, if thequalifiedName, or its prefix, is "xmlns" and thenamespaceURIis different from "http://www.w3.org/2000/xmlns/".

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

The attributesnodeName,nodeValueandattributesare 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 specificnodeType(e.g.,nodeValuefor anElementorattributesfor aComment), this returnsnull. 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.

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

The node is anElement.

The node is anAttr.

The node is aTextnode.

The node is aCDATASection.

The node is anEntityReference.

The node is anEntity.

The node is aProcessingInstruction.

The node is aComment.

The node is aDocument.

The node is aDocumentType.

The node is aDocumentFragment.

The node is aNotation.

The values ofnodeName,nodeValue, andattributesvary according to the node type as follows:
InterfacenodeNamenodeValueattributes
Attrsame asAttr.namesame asAttr.valuenull
CDATASection"#cdata-section"same asCharacterData.data, the content of the CDATA Sectionnull
Comment"#comment"same asCharacterData.data, the content of the commentnull
Document"#document"nullnull
DocumentFragment"#document-fragment"nullnull
DocumentTypesame asDocumentType.namenullnull
Elementsame asElement.tagNamenullNamedNodeMap
Entityentity namenullnull
EntityReferencename of entity referencednullnull
Notationnotation namenullnull
ProcessingInstructionsame asProcessingInstruction.targetsame asProcessingInstruction.datanull
Text"#text"same asCharacterData.data, the content of the text nodenull

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 benull, setting it has no effect, including if the node isread-only.

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

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

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

Theparentof this node. All nodes, exceptAttr,Document,DocumentFragment,Entity, andNotationmay 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 isnull.

ANodeListthat contains all children of this node. If there are no children, this is aNodeListcontaining no nodes.

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

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

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

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

ANamedNodeMapcontaining the attributes of this node (if it is anElement) ornullotherwise.

TheDocumentobject associated with this node. This is also theDocumentobject used to create new nodes. When this node is aDocumentor aDocumentTypewhich is not used with anyDocumentyet, this isnull.

Inserts the nodenewChildbefore the existing child noderefChild. IfrefChildisnull, insertnewChildat the end of the list of children.

IfnewChildis aDocumentFragmentobject, all of its children are inserted, in the same order, beforerefChild. If thenewChildis already in the tree, it is first removed.

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 thenewChildnode, or if the node to insert is one of this node'sancestorsor this node itself, or if this node is of typeDocumentand the DOM application attempts to insert a secondDocumentTypeorElementnode.

WRONG_DOCUMENT_ERR: Raised ifnewChildwas 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 ifrefChildis not a child of this node.

NOT_SUPPORTED_ERR: if this node is of typeDocument, this exception might be raised if the DOM implementation doesn't support the insertion of aDocumentTypeorElementnode.

Replaces the child nodeoldChildwithnewChildin the list of children, and returns theoldChildnode.

IfnewChildis aDocumentFragmentobject,oldChildis replaced by all of theDocumentFragmentchildren, which are inserted in the same order. If thenewChildis already in the tree, it is first removed.

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 thenewChildnode, or if the node to put in is one of this node'sancestorsor this node itself, or if this node is of typeDocumentand the result of the replacement operation would add a secondDocumentTypeorElementon theDocumentnode.

WRONG_DOCUMENT_ERR: Raised ifnewChildwas 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 ifoldChildis not a child of this node.

NOT_SUPPORTED_ERR: if this node is of typeDocument, this exception might be raised if the DOM implementation doesn't support the replacement of theDocumentTypechild orElementchild.

Removes the child node indicated byoldChildfrom 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 ifoldChildis not a child of this node.

NOT_SUPPORTED_ERR: if this node is of typeDocument, this exception might be raised if the DOM implementation doesn't support the removal of theDocumentTypechild or theElementchild.

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

The node to add.

If it is aDocumentFragmentobject, 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 thenewChildnode, or if the node to append is one of this node'sancestorsor this node itself, or if this node is of typeDocumentand the DOM application attempts to append a secondDocumentTypeorElementnode.

WRONG_DOCUMENT_ERR: Raised ifnewChildwas 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 thenewChildnode is a child of theDocumentnode, this exception might be raised if the DOM implementation doesn't support the removal of theDocumentTypechild orElementchild.

Returns whether this node has any children.

Returnstrueif this node has any children,falseotherwise.

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

Cloning anElementcopies 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 theElementsince the text is contained in a childTextnode. Cloning anAttrdirectly, as opposed to be cloned as part of anElementcloning operation, returns a specified attribute (specifiedistrue). Cloning anAttralways clones its children, since they represent its value, no matter whether this is a deep clone or not. Cloning anEntityReferenceautomatically constructs its subtree if a correspondingEntityis 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 anEntityReferenceclone arereadonly. In addition, clones of unspecifiedAttrnodes are specified. And, cloningDocument,DocumentType,Entity, andNotationnodes is implementation dependent.

Iftrue, recursively clone the subtree under the specified node; iffalse, clone only the node itself (and its attributes, if it is anElement).

The duplicate node.

Puts allTextnodes in the full depth of the sub-tree underneath thisNode, including attribute nodes, into a "normal" form where only structure (e.g., elements, comments, processing instructions, CDATA sections, and entity references) separatesTextnodes, i.e., there are neither adjacentTextnodes nor emptyTextnodes. 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 XPointerlookups) that depend on a particular document tree structure are to be used. If the parameter "normalize-characters" of theDOMConfigurationobject attached to theNode.ownerDocumentistrue, this method will also fully normalize the characters of theTextnodes.

In cases where the document containsCDATASections, the normalize operation alone may not be sufficient, since XPointers do not differentiate betweenTextnodes andCDATASectionnodes.

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

The name of the feature to test.

This is the version number of the feature to test.

Returnstrueif the specified feature is supported on this node,falseotherwise.

Thenamespace URIof this node, ornullif it is unspecified (see).

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 thanELEMENT_NODEandATTRIBUTE_NODEand nodes created with a DOM Level 1 method, such asDocument.createElement(), this is alwaysnull.

Per theNamespaces in XMLSpecificationan 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.

Thenamespace prefixof this node, ornullif it is unspecified. When it is defined to benull, setting it has no effect, including if the node isread-only.

Note that setting this attribute, when permitted, changes thenodeNameattribute, which holds thequalified name, as well as thetagNameandnameattributes of theElementandAttrinterfaces, when applicable.

Setting the prefix tonullmakes 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 thenamespaceURIandlocalNamedo not change.

For nodes of any type other thanELEMENT_NODEandATTRIBUTE_NODEand nodes created with a DOM Level 1 method, such ascreateElementfrom theDocumentinterface, this is alwaysnull.

INVALID_CHARACTER_ERR: Raised if the specified prefix contains an illegal character according to the XML version in use specified in theDocument.xmlVersionattribute.

NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.

NAMESPACE_ERR: Raised if the specifiedprefixis malformed per the Namespaces in XML specification, if thenamespaceURIof this node isnull, if the specified prefix is "xml" and thenamespaceURIof 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 thenamespaceURIof this node is different from "http://www.w3.org/2000/xmlns/", or if this node is an attribute and thequalifiedNameof this node is "xmlns".

Returns the local part of thequalified nameof this node.

For nodes of any type other thanELEMENT_NODEandATTRIBUTE_NODEand nodes created with a DOM Level 1 method, such asDocument.createElement(), this is alwaysnull.

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

Returnstrueif this node has any attributes,falseotherwise.

The absolute base URI of this node ornullif the implementation wasn't able to obtain an absolute URI. This value is computed as described in. However, when theDocumentsupports the feature "HTML", the base URI is computed using first the value of the href attribute of the HTML BASE element if any, and the value of thedocumentURIattribute from theDocumentinterface 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 ofnodeTypethan 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 andnodeTypeis 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 thedocument 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 benull, 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 ornull, replaced by a singleTextnode 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 attributeText.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:

Node typeContent
ELEMENT_NODE, ATTRIBUTE_NODE, ENTITY_NODE, ENTITY_REFERENCE_NODE, DOCUMENT_FRAGMENT_NODEconcatenation of thetextContentattribute value of every child node, excluding COMMENT_NODE and PROCESSING_INSTRUCTION_NODE nodes. This is the empty string if the node has no children.
TEXT_NODE, CDATA_SECTION_NODE, COMMENT_NODE, PROCESSING_INSTRUCTION_NODEnodeValue
DOCUMENT_NODE, DOCUMENT_TYPE_NODE, NOTATION_NODEnull

NO_MODIFICATION_ALLOWED_ERR: Raised when the node is readonly.

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

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

This method provides a way to determine whether twoNodereferences returned by the implementation reference the same object. When twoNodereferences 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.

Returnstrueif the nodes are the same,falseotherwise.

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

Seefor details on the algorithm used by this method.

The namespace URI to look for.

Returns an associated namespace prefix if found ornullif 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 specifiednamespaceURIis the default namespace or not.

The namespace URI to look for.

Returnstrueif the specifiednamespaceURIis the default namespace,falseotherwise.

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

Seefor details on the algorithm used by this method.

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

Returns the associated namespace URI ornullif 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 withNode.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 bothnull, or they have the same length and are character for character identical.

TheattributesNamedNodeMapsare equal. This is: they are bothnull, 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.

ThechildNodesNodeListsare equal. This is: they are bothnull, 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 twoDocumentTypenodes to be equal, the following conditions must also be satisfied:

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

TheentitiesNamedNodeMapsare equal.

ThenotationsNamedNodeMapsare equal.

On the other hand, the following do not affect equality: theownerDocument,baseURI, andparentNodeattributes, thespecifiedattribute forAttrnodes, theschemaTypeInfoattribute forAttrandElementnodes, theText.isElementContentWhitespaceattribute forTextnodes, as well as any user data or event listeners registered on the nodes.

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.

Returnstrueif the nodes are equal,falseotherwise.

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

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, ornullif there is no object which implements interfaces associated with that feature. If theDOMObjectreturned by this method implements theNodeinterface, it must delegate to the primary coreNodeand not return results inconsistent with the primary coreNodesuch as attributes, childNodes, etc.

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

The key to associate the object to.

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

The handler to associate to that key, ornull.

Returns theDOMUserDatapreviously associated to the given key on this node, ornullif 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 callingsetUserDatawith the same key.

The key the object is associated to.

Returns theDOMUserDataassociated to the given key on this node, ornullif there was none.

TheNodeListinterface provides the abstraction of an ordered collection of nodes, without defining or constraining how this collection is implemented.NodeListobjects in the DOM arelive.

The items in theNodeListare accessible via an integral index, starting from 0.

Returns theindexth item in the collection. Ifindexis greater than or equal to the number of nodes in the list, this returnsnull.

Index into the collection.

The node at theindexth position in theNodeList, ornullif that is not a valid index.

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

Objects implementing theNamedNodeMapinterface are used to represent collections of nodes that can be accessed by name. Note thatNamedNodeMapdoes not inherit fromNodeList;NamedNodeMapsare not maintained in any particular order. Objects contained in an object implementingNamedNodeMapmay also be accessed by an ordinal index, but this is simply to allow convenient enumeration of the contents of aNamedNodeMap, and does not imply that the DOM specifies an order to these Nodes.

NamedNodeMapobjects in the DOM arelive.

Retrieves a node specified by name.

ThenodeNameof a node to retrieve.

ANode(of any type) with the specifiednodeName, ornullif it does not identify any node in this map.

Adds a node using itsnodeNameattribute. 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 thenodeNameattribute 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 itsnodeNameattribute.

If the newNodereplaces an existing node the replacedNodeis returned, otherwisenullis returned.

WRONG_DOCUMENT_ERR: Raised ifargwas 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 ifargis anAttrthat is already an attribute of anotherElementobject. The DOM user must explicitly cloneAttrnodes 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.

ThenodeNameof 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 namednamein this map.

NO_MODIFICATION_ALLOWED_ERR: Raised if this map is readonly.

Returns theindexth item in the map. Ifindexis greater than or equal to the number of nodes in this map, this returnsnull.

Index into this map.

The node at theindexth position in the map, ornullif that is not a valid index.

The number of nodes in this map. The range of valid child node indices is0tolength-1inclusive.

Retrieves a node specified by local name and namespace URI.

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

Thenamespace URIof the node to retrieve.

Thelocal nameof the node to retrieve.

ANode(of any type) with the specified local name and namespace URI, ornullif 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).

Adds a node using itsnamespaceURIandlocalName. 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, 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 itsnamespaceURIandlocalNameattributes.

If the newNodereplaces an existing node the replacedNodeis returned, otherwisenullis returned.

WRONG_DOCUMENT_ERR: Raised ifargwas 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 ifargis anAttrthat is already an attribute of anotherElementobject. The DOM user must explicitly cloneAttrnodes 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).

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 theNodeinterface. If so, an attribute immediately appears containing the default value as well as the corresponding namespace URI, local name, and prefix when applicable.

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

Thenamespace URIof the node to remove.

Thelocal nameof 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 specifiednamespaceURIandlocalNamein 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).

TheCharacterDatainterface 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 toCharacterData, thoughTextand others do inherit the interface from it. Alloffsetsin this interface start from0.

As explained in theDOMStringinterface, text strings in the DOM are represented in UTF-16, i.e. as a sequence of 16-bit units. In the following, the term16-bit unitsis 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 aCharacterDatanode. However, implementation limits may mean that the entirety of a node's data may not fit into a singleDOMString. In such cases, the user may callsubstringDatato 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 aDOMStringvariable on the implementation platform.

The number of16-bit unitsthat are available throughdataand thesubstringDatamethod below. This may have the value zero, i.e.,CharacterDatanodes 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 ofoffsetandcountexceeds thelength, then all 16-bit units to the end of the data are returned.

INDEX_SIZE_ERR: Raised if the specifiedoffsetis negative or greater than the number of 16-bit units indata, or if the specifiedcountis negative.

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

Append the string to the end of the character data of the node. Upon success,dataprovides access to the concatenation ofdataand theDOMStringspecified.

TheDOMStringto append.

NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.

Insert a string at the specified16-bit unitoffset.

The character offset at which to insert.

TheDOMStringto insert.

INDEX_SIZE_ERR: Raised if the specifiedoffsetis negative or greater than the number of 16-bit units indata.

NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.

Remove a range of16-bit unitsfrom the node. Upon success,dataandlengthreflect the change.

The offset from which to start removing.

The number of 16-bit units to delete. If the sum ofoffsetandcountexceedslengththen all 16-bit units fromoffsetto the end of the data are deleted.

INDEX_SIZE_ERR: Raised if the specifiedoffsetis negative or greater than the number of 16-bit units indata, or if the specifiedcountis negative.

NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.

Replace the characters starting at the specified16-bit unitoffset with the specified string.

The offset from which to start replacing.

The number of 16-bit units to replace. If the sum ofoffsetandcountexceedslength, then all 16-bit units to the end of the data are replaced; (i.e., the effect is the same as aremovemethod call with the same range, followed by anappendmethod invocation).

TheDOMStringwith which the range must be replaced.

INDEX_SIZE_ERR: Raised if the specifiedoffsetis negative or greater than the number of 16-bit units indata, or if the specifiedcountis negative.

NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.

TheAttrinterface represents an attribute in anElementobject. Typically the allowable values for the attribute are defined in a schema associated with the document.

Attrobjects inherit theNodeinterface, 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, theNodeattributesparentNode,previousSibling, andnextSiblinghave anullvalue forAttrobjects. 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,Attrnodes may not be immediate children of aDocumentFragment. However, they can be associated withElementnodes contained within aDocumentFragment. In short, users and implementors of the DOM need to be aware thatAttrnodes have some things in common with other objects inheriting theNodeinterface, 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 theNode.nodeValueattribute on theAttrinstance 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 withspecifiedset tofalse. Removing attribute nodes for which a default value is defined in the schema generates a new attribute node with the default value andspecifiedset tofalse. If validation occurred while invokingDocument.normalizeDocument(), attribute nodes withspecifiedequals tofalseare 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 theAttrnode may be eitherTextorEntityReferencenodes (when these are in use; see the description ofEntityReferencefor 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 astokenized.

The way attribute value normalization is performed by the DOM implementation depends on how much the implementation knows about the schema in use. Typically, thevalueandnodeValueattributes of anAttrnode initially returns the normalized value given by the parser. It is also the case afterDocument.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 theAttrchild nodes. In particular, this is true whencharacter referencesare 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:

ExamplesParsed attribute valueInitialAttr.valueSerialized attribute value
Character reference"x²=5""x²=5""x²=5"
Built-in character entity"y&lt;6""y<6""y&lt;6"
Literal newline between"x=5&#10;y=6""x=5 y=6""x=5&#10;y=6"
Normalized newline between"x=5 y=6""x=5 y=6""x=5 y=6"
Entityewith literal newline<!ENTITY e '...&#10;...'> [...]> "x=5&e;y=6"Dependent on Implementation and Load OptionsDependent on Implementation and Load/Save Options

Returns the name of this attribute. IfNode.localNameis different fromnull, this attribute is aqualified name.

Trueif this attribute was explicitly given a value in the instance document,falseotherwise. 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 totrue. The implementation may handle attributes with default values from other schemas similarly but applications should useDocument.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 methodgetAttributeon theElementinterface.

On setting, this creates aTextnode 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 methodElement.setAttribute().

Some specialized implementations, such as someimplementations, 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.

TheElementnode this attribute is attached to ornullif 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 invokingDocument.normalizeDocument(),schemaTypeInfomay 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, theownerElementof this attribute can be retrieved using the methodDocument.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 Schemawhile loading the document or while invokingDocument.normalizeDocument(), the post-schema-validation infoset contributions (PSVI contributions) values are used to determine if this attribute is aschema-determined ID attributeusing theschema-determined IDdefinition in.

If validation occurred using a DTD while loading the document or while invokingDocument.normalizeDocument(), the infoset[type definition]value is used to determine if this attribute is aDTD-determined ID attributeusing theDTD-determined IDdefinition in.

from the use of the methodsElement.setIdAttribute(),Element.setIdAttributeNS(), orElement.setIdAttributeNode(), i.e. it is anuser-determined ID attribute;

XPointer framework (see section 3.2 in) consider the DOMuser-determined ID attributeas being part of the XPointerexternally-determined IDdefinition.

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

If validation occurred while invokingDocument.normalizeDocument(), alluser-determined ID attributesare reset and all attribute nodes ID information are then reevaluated in accordance to the schema used. As a consequence, if theAttr.schemaTypeInfoattribute contains an ID type,isIdwill always return true.

TheElementinterface represents anelementin an HTML or XML document. Elements may have attributes associated with them; since theElementinterface inherits fromNode, the genericNodeinterface attributeattributesmay be used to retrieve the set of all attributes for an element. There are methods on theElementinterface to retrieve either anAttrobject by name or an attribute value by name. In XML, where an attribute value may contain entity references, anAttrobject 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 aconvenience.

In DOM Level 2, the methodnormalizeis inherited from theNodeinterface where it was moved.

The name of the element. IfNode.localNameis different fromnull, this attribute is aqualified name. For example, in:<elementExample id="demo"> ... </elementExample> ,tagNamehas the value"elementExample". Note that this is case-preserving in XML, as are all of the operations of the DOM. The HTML DOM returns thetagNameof an HTML element in the canonical uppercase form, regardless of the case in the source HTML document.

Retrieves an attribute value by name.

The name of the attribute to retrieve.

TheAttrvalue 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 anAttrnode plus anyTextandEntityReferencenodes, build the appropriate subtree, and usesetAttributeNodeto assign it as the value of an attribute.

To set an attribute with a qualified name and namespace URI, use thesetAttributeNSmethod.

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 theDocument.xmlVersionattribute.

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 useDocument.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 theremoveAttributeNSmethod.

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 thegetAttributeNodeNSmethod.

The name (nodeName) of the attribute to retrieve.

TheAttrnode with the specified name (nodeName) ornullif 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 thesetAttributeNodeNSmethod.

TheAttrnode to add to the attribute list.

If thenewAttrattribute replaces an existing attribute, the replacedAttrnode is returned, otherwisenullis returned.

WRONG_DOCUMENT_ERR: Raised ifnewAttrwas 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 ifnewAttris already an attribute of anotherElementobject. The DOM user must explicitly cloneAttrnodes to re-use them in other elements.

Removes the specified attribute node. If a default value for the removedAttrnode 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 useDocument.normalizeDocument()to guarantee this information is up-to-date.

TheAttrnode to remove from the attribute list.

TheAttrnode that was removed.

NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.

NOT_FOUND_ERR: Raised ifoldAttris not an attribute of the element.

Returns aNodeListof alldescendantElementswith a given tag name, indocument order.

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

A list of matchingElementnodes.

Retrieves an attribute value by local name and namespace URI.

Per, applications must use the valuenullas thenamespaceURIparameter for methods if they wish to have no namespace.

Thenamespace URIof the attribute to retrieve.

Thelocal nameof the attribute to retrieve.

TheAttrvalue 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).

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 thequalifiedName, and its value is changed to be thevalueparameter. 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 anAttrnode plus anyTextandEntityReferencenodes, build the appropriate subtree, and usesetAttributeNodeNSorsetAttributeNodeto assign it as the value of an attribute.

Per, applications must use the valuenullas thenamespaceURIparameter for methods if they wish to have no namespace.

Thenamespace URIof the attribute to create or alter.

Thequalified nameof 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 theDocument.xmlVersionattribute.

NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.

NAMESPACE_ERR: Raised if thequalifiedNameis malformed per the Namespaces in XML specification, if thequalifiedNamehas a prefix and thenamespaceURIisnull, if thequalifiedNamehas a prefix that is "xml" and thenamespaceURIis different from "http://www.w3.org/XML/1998/namespace", if thequalifiedNameor its prefix is "xmlns" and thenamespaceURIis different from "http://www.w3.org/2000/xmlns/", or if thenamespaceURIis "http://www.w3.org/2000/xmlns/" and neither thequalifiedNamenor 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).

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 useDocument.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, applications must use the valuenullas thenamespaceURIparameter for methods if they wish to have no namespace.

Thenamespace URIof the attribute to remove.

Thelocal nameof 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).

Retrieves anAttrnode by local name and namespace URI.

Per, applications must use the valuenullas thenamespaceURIparameter for methods if they wish to have no namespace.

Thenamespace URIof the attribute to retrieve.

Thelocal nameof the attribute to retrieve.

TheAttrnode with the specified attribute local name and namespace URI ornullif 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).

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, applications must use the valuenullas thenamespaceURIparameter for methods if they wish to have no namespace.

TheAttrnode to add to the attribute list.

If thenewAttrattribute replaces an existing attribute with the samelocal nameandnamespace URI, the replacedAttrnode is returned, otherwisenullis returned.

WRONG_DOCUMENT_ERR: Raised ifnewAttrwas 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 ifnewAttris already an attribute of anotherElementobject. The DOM user must explicitly cloneAttrnodes 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).

Returns aNodeListof all thedescendantElementswith a given local name and namespace URI indocument order.

Thenamespace URIof the elements to match on. The special value "*" matches all namespaces.

Thelocal nameof the elements to match on. The special value "*" matches all local names.

A newNodeListobject containing all the matchedElements.

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).

Returnstruewhen an attribute with a given name is specified on this element or has a default value,falseotherwise.

The name of the attribute to look for.

trueif an attribute with the given name is specified on this element or has a default value,falseotherwise.

Returnstruewhen an attribute with a given local name and namespace URI is specified on this element or has a default value,falseotherwise.

Per, applications must use the valuenullas thenamespaceURIparameter for methods if they wish to have no namespace.

Thenamespace URIof the attribute to look for.

Thelocal nameof the attribute to look for.

trueif an attribute with the given local name and namespace URI is specified or has a default value on this element,falseotherwise.

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).

The type information associated with this element.

If the parameterisIdistrue, this method declares the specified attribute to be auser-determined ID attribute. This affects the value ofAttr.isIdand the behavior ofDocument.getElementById, but does not change any schema that may be in use, in particular this does not affect theAttr.schemaTypeInfoof the specifiedAttrnode. Use the valuefalsefor the parameterisIdto undeclare an attribute for being auser-determined ID attribute.

To specify an attribute by local name and namespace URI, use thesetIdAttributeNSmethod.

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 parameterisIdistrue, this method declares the specified attribute to be auser-determined ID attribute. This affects the value ofAttr.isIdand the behavior ofDocument.getElementById, but does not change any schema that may be in use, in particular this does not affect theAttr.schemaTypeInfoof the specifiedAttrnode. Use the valuefalsefor the parameterisIdto undeclare an attribute for being auser-determined ID attribute.

Thenamespace URIof the attribute.

Thelocal nameof 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 parameterisIdistrue, this method declares the specified attribute to be auser-determined ID attribute. This affects the value ofAttr.isIdand the behavior ofDocument.getElementById, but does not change any schema that may be in use, in particular this does not affect theAttr.schemaTypeInfoof the specifiedAttrnode. Use the valuefalsefor the parameterisIdto undeclare an attribute for being auser-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.

TheTextinterface inherits fromCharacterDataand represents the textual content (termedcharacter datain XML) of anElementorAttr. If there is no markup inside an element's content, the text is contained in a single object implementing theTextinterface that is the only child of the element. If there is markup, it is parsed into theinformation items(elements, comments, etc.) andTextnodes that form the list of children of the element.

When a document is first made available via the DOM, there is only oneTextnode for each block of text. Users may create adjacentTextnodes 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. TheNode.normalize()method merges any such adjacentTextobjects into a single node for each block of text.

No lexical check is done on the content of aTextnode 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 specifiedoffset, keeping both in the tree assiblings. After being split, this node will contain all the content up to theoffsetpoint. A new node of the same type, which contains all the content at and after theoffsetpoint, is returned. If the original node had a parent node, the new node is inserted as the nextsiblingof the original node. When theoffsetis equal to the length of this node, the new node has no data.

The16-bit unitoffset at which to split, starting from0.

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 indata.

NO_MODIFICATION_ALLOWED_ERR: Raised if this node is readonly.

Returns whether this text node containselement 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 usingDocument.normalizeDocument().

Returns all text ofTextnodeslogically-adjacent text nodesto this node, concatenated in document order.

For instance, in the example belowwholeTexton theTextnode that contains "bar" returns "barfoo", while on theTextnode that contains "foo" it returns "barfoo".

Replaces the text of the current node and alllogically-adjacent text nodeswith the specified text. Alllogically-adjacent text nodesare 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 isread-only;

a newTextnode of the same type (TextorCDATASection) as the current node inserted at the location of the replacement.

For instance, in the above example callingreplaceWholeTexton theTextnode that contains "bar" with "yo" in argument results in the following:

Where the nodes to be removed are read-only descendants of anEntityReference, theEntityReferencemust be removed instead of the read-only nodes. If anyEntityReferenceto be removed has descendants that are notEntityReference,Text, orCDATASectionnodes, thereplaceWholeTextmethod must fail before performing any modification of the document, raising aDOMExceptionwith the codeNO_MODIFICATION_ALLOWED_ERR.

For instance, in the example below callingreplaceWholeTexton theTextnode that contains "bar" fails, because theEntityReferencenode "ent" contains anElementnode which cannot be removed.

The content of the replacingTextnode.

TheTextnode created with the specified content.

NO_MODIFICATION_ALLOWED_ERR: Raised if one of theTextnodes being replaced is readonly.

This interface inherits fromCharacterDataand 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. The presence of this character sequence must generate a fatal error during serialization.

TheTypeInfointerface represents a type referenced fromElementorAttrnodes, specified in theschemasassociated with the document. The type is a pair of anamespace URIand name properties, and depends on the document's schema.

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

If this type is referenced from anAttrnode,typeNamespaceis"http://www.w3.org/TR/REC-xml"andtypeNamerepresents the[attribute type]property in the. If there is no declaration for the attribute,typeNamespaceandtypeNamearenull.

If this type is referenced from anElementnode,typeNamespaceandtypeNamearenull.

If the document's schema is an XML Schema, 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, otherwisenull.

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":

If[member type definition]exists:

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

Otherwise, expose the namespace and local name of the correspondinganonymous type name.

If the[type definition]property exists:

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

Otherwise, expose the namespace and local name of the correspondinganonymous type name.

If the[member type definition anonymous]exists:

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

Otherwise, expose the namespace and local name of the correspondinganonymous type name.

If the[type definition anonymous]exists:

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

Otherwise, expose the namespace and local name of the correspondinganonymous type name.

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

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

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

These are the available values for thederivationMethodparameter used by the methodTypeInfo.isDerivedFrom(). It is a set of possible types of derivation, and the values represent bit positions. If a bit in thederivationMethodparameter is set to1, 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 theisDerivedFrommethod, combining all of them in thederivationMethodparameter 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 fromxsd:anyType.

any simple type derives fromxsd:anySimpleTypebyrestriction.

any complex type does not derive fromxsd:anySimpleTypebyrestriction.

If the document's schema is an XML Schema, this constant represents the derivation byrestrictionif complex types are involved, or arestrictionif simple types are involved.

The reference type definition is derived byrestrictionfrom 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 thederivation methodsinvolved arerestriction.

If the document's schema is an XML Schema, this constant represents the derivation byextension.

The reference type definition is derived byextensionfrom 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 thederivation methodsinvolved is anextension.

If the document's schema is an XML Schema, this constant represents theunionif simple types are involved.

The reference type definition is derived byunionfrom the other type definition if there exists two type definitions T1 and T2 such as the reference type definition is derived from T1 byDERIVATION_RESTRICTIONorDERIVATION_EXTENSION, T2 is derived from the other type definition byDERIVATION_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, this constant represents thelist.

The reference type definition is derived bylistfrom the other type definition if there exists two type definitions T1 and T2 such as the reference type definition is derived from T1 byDERIVATION_RESTRICTIONorDERIVATION_EXTENSION, T2 is derived from the other type definition byDERIVATION_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. theTypeInfoon 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 returnfalse.

If the document's schema is an XML Schema, the method willtrueif the reference type definition is derived from the other type definition according to the derivation parameter. If the value of the parameter is0(no bit is set to1for thederivationMethodparameter), the method will returntrueif 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 usingNode.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, usingNode.cloneNode().

The node is imported, usingDocument.importNode().

The node is deleted.

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, usingDocument.renameNode().

The node is adopted, usingDocument.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 aUserDataHandler. 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 isnullwhen the node is being deleted.

Specifies the node newly created if any, ornull.

DOMErroris an interface that describes an error.

An integer indicating the severity of the error.

The severity of the error described by theDOMErroris warning. ASEVERITY_WARNINGwill not cause the processing to stop, unlessDOMErrorHandler.handleError()returnsfalse.

The severity of the error described by theDOMErroris error. ASEVERITY_ERRORmay not cause the processing to stop if the error can be recovered, unlessDOMErrorHandler.handleError()returnsfalse.

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

The severity of the error, eitherSEVERITY_WARNING,SEVERITY_ERROR, orSEVERITY_FATAL_ERROR.

An implementation specific string describing the error that occurred.

ADOMStringindicating which related data is expected inrelatedData. Users should refer to the specification of the error in order to find itsDOMStringtype andrelatedDatadefinitions if any.

As an example,Document.normalizeDocument()does generate warnings when the "split-cdata-sections" parameter is in use. Therefore, the method generates aSEVERITY_WARNINGwithtype"cdata-sections-splitted"and the firstCDATASectionnode in document order resulting from the split is returned by therelatedDataattribute.

The related platform dependent exception if any.

The relatedDOMError.typedependent data if any.

The location of the error.

DOMErrorHandleris 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). ADOMErrorHandlerobject can be attached to aDocumentusing the "error-handler" on theDOMConfigurationinterface. 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 returningtrue.

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

If thehandleErrormethod returnsfalse, the DOM implementation should stop the current processing when possible. If the method returnstrue, the processing may continue depending onDOMError.severity.

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

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

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

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

The UTF-16, as defined inand Amendment 1 of, offset into the input source this locator is pointing to or-1if there is no UTF-16 offset available.

The node this locator is pointing to, ornullif no node is available.

The URI this locator is pointing to, ornullif no URI is available.

TheDOMConfigurationinterface represents the configuration of a document and maintains a table of recognized parameters. Using the configuration, it is possible to changeDocument.normalizeDocument()behavior, such as replacing theCDATASectionnodes withTextnodes or specifying the type of theschemathat must be used when the validation of theDocumentis requested.DOMConfigurationobjects are also used inin theDOMParserandDOMSerializerinterfaces.

The parameter names used by theDOMConfigurationobject 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, names are recommended to follow the section5.16 Identifiersofwith 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.

Parameters are similar to features and properties used in SAX2.

The following list of parameters defined in the DOM:

[optional]

Canonicalize the document according to the rules specified in, such as removing theDocumentTypenode (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 totruewill also set the state of the parameters listed below. Later changes to the state of one of those parameters will revert "canonical-form" back tofalse.

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

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

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

[required] (default)

Do not canonicalize the document.

[required] (default)

KeepCDATASectionnodes in the document.

[required]

TransformCDATASectionnodes in the document intoTextnodes. The newTextnode is then combined with any adjacentTextnode.

[optional]

Check if the characters in the document arefully normalized, as defined in appendix B of. When a sequence of characters is encountered that fails normalization checking, an error with theDOMError.typeequals to "check-character-normalization-failure" is issued.

[required] (default)

Do not check if characters are normalized.

[required] (default)

KeepCommentnodes in the document.

[required]

DiscardCommentnodes in the document.

[optional]

Expose schema normalized values in the tree, such asXML Schema normalized valuesin the case of XML Schema. Since this parameter requires to haveschemainformation, the "validate" parameter will also be set totrue. Having this parameter activated when "validate" isfalsehas no effect and no schema-normalization will happen.

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 ofand is only meant forschemalanguages other than Document Type Definition (DTD).

[required] (default)

Do not perform schema normalization on the tree.

[required] (default)

Keep all whitespaces in the document.

[optional]

Discard allTextnodes that contain whitespaces in element content, as described in[element content whitespace]. The implementation is expected to use the attributeText.isElementContentWhitespaceto determine if aTextnode should be discarded or not.

[required] (default)

KeepEntityReferencenodes in the document.

[required]

Remove allEntityReferencenodes from the document, putting the entity expansions directly in their place.Textnodes are normalized, as defined inNode.normalize. Onlyunexpanded entity referencesare kept in the document.

This parameter does not affectEntitynodes.

[required]

Contains aDOMErrorHandlerobject. If an error is encountered in the document, the implementation will call back theDOMErrorHandlerregistered using this parameter. The implementation may provide a defaultDOMErrorHandlerobject.

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

[required]

Keep in the document the information defined in the XML Information Set.

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

This forces the following parameters totrue: "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 withgetParameterreturnstrueonly if the individual parameters specified above are appropriately set.

Settinginfosettofalsehas no effect.

[required] (default)

Perform the namespace processing as defined in.

[optional]

Do not perform the namespace processing.

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

[required] (default)

Include namespace declaration attributes, specified or defaulted from theschema, in the document. See also the sections "Declaring Namespaces" inand.

[required]

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

[optional]

Fully normalizedthe characters in the document as defined in appendix B of.

[required] (default)

Do not perform character normalization.

[optional]

Represent aDOMStringobject containing a list of URIs, separated by whitespaces (characters matching thenonterminal production Sdefined in section 2.3), that represents theschemasagainst which validation should occur, i.e. the current schema. The types of schemas referenced in this list must match the type specified withschema-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 theschemaLocationattribute) in a schema document (i.e. using schemaimportmechanisms) share the sametargetNamespace, the schema specified by the user using this property will be used. If two schemas specified using this property share the sametargetNamespaceor have no namespace, the behavior is implementation dependent.

If no location has been provided, this parameter isnull.

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

[optional]

Represent aDOMStringobject containing an absolute URI and representing the type of theschemalanguage 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 isnull.

For XML Schema, applications must use the value"http://www.w3.org/2001/XMLSchema". For XML DTD, 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.

[required] (default)

Split CDATA sections containing the CDATA section termination marker ']]>'. When a CDATA section is split a warning is issued with aDOMError.typeequals to"cdata-sections-splitted"andDOMError.relatedDataequals to the firstCDATASectionnode in document order resulting from the split.

[required]

Signal an error if aCDATASectioncontains an unrepresentable character.

[optional]

Require the validation against aschema(i.e. XML schema, DTD, any other type or representation of schema) of the document as it is being normalized as defined by. 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" istrue.

This parameter will reevaluate:

Attribute nodes withAttr.specifiedequals tofalse, as specified in the description of theAttrinterface;

The value of the attributeText.isElementContentWhitespacefor allTextnodes;

The value of the attributeAttr.isIdfor allAttrnodes;

The attributesElement.schemaTypeInfoandAttr.schemaTypeInfo.

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

[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" istrue.

[optional]

Enable validation only if a declaration for the document element can be found in aschema(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 totrue.

"validate-if-schema" and "validate" are mutually exclusive, setting one of them totruewill set the other one tofalse.

[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" istrue.

[required] (default)

Check if all nodes are XMLwell formedaccording to the XML version in use inDocument.xmlVersion:

check if the attributeNode.nodeNamecontains invalid characters according to its node type and generate aDOMErrorof type"wf-invalid-character-in-node-name", with aDOMError.SEVERITY_ERRORseverity, if necessary;

check if the text content insideAttr,Element,Comment,Text,CDATASectionnodes for invalid characters and generate aDOMErrorof type"wf-invalid-character", with aDOMError.SEVERITY_ERRORseverity, if necessary;

check if the data insideProcessingInstructionnodes for invalid characters and generate aDOMErrorof type"wf-invalid-character", with aDOMError.SEVERITY_ERRORseverity, if necessary;

[optional]

Do not check for XML well-formedness.

The resolution of the system identifiers associated with entities is done usingDocument.documentURI. However, when the feature "LS" defined inis supported by the DOM implementation, the parameter "resource-resolver" can also be used onDOMConfigurationobjects attached toDocumentnodes. If this parameter is set,Document.normalizeDocument()will invoke the resource resolver instead of usingDocument.documentURI.

Set the value of a parameter.

The name of the parameter to set.

The new value ornullif the user wishes to unset the parameter. While the type of the value parameter is defined asDOMUserData, 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 typeDOMErrorHandler.

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 ornullif 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. ifnull, the returned value istrue.

trueif the parameter could be successfully set to the specified value, orfalseif 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 thisDOMConfigurationobject 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.

CDATA sections are used to escape blocks of text containing characters that would otherwise be regarded as markup. The only delimiter that is recognized in a CDATA section is the "]]>" string that ends the CDATA section. CDATA sections cannot be nested. Their primary purpose is for including material such as XML fragments, without needing to escape all the delimiters.

TheCharacterData.dataattribute holds the text that is contained by the CDATA section. Note that thismaycontain characters that need to be escaped outside of CDATA sections and that, depending on the character encoding ("charset") chosen for serialization, it may be impossible to write out some characters as part of a CDATA section.

TheCDATASectioninterface inherits from theCharacterDatainterface through theTextinterface. AdjacentCDATASectionnodes are not merged by use of thenormalizemethod of theNodeinterface.

No lexical check is done on the content of a CDATA section and it is therefore possible to have the character sequence"]]>"in the content, which is illegal in a CDATA section per section 2.7 of. The presence of this character sequence must generate a fatal error during serialization or the cdata section must be splitted before the serialization (see also the parameter"split-cdata-sections"in theDOMConfigurationinterface).

Because no markup is recognized within aCDATASection, character numeric references cannot be used as an escape mechanism when serializing. Therefore, action needs to be taken when serializing aCDATASectionwith a character encoding where some of the contained characters cannot be represented. Failure to do so would not produce well-formed XML.

One potential solution in the serialization process is to end the CDATA section before the character, output the character using a character reference or entity reference, and open a new CDATA section for any further characters in the text node. Note, however, that some code conversion libraries at the time of writing do not return an error or exception when a character is missing from the encoding, making the task of ensuring that data is not corrupted on serialization more difficult.

EachDocumenthas adoctypeattribute whose value is eithernullor aDocumentTypeobject. TheDocumentTypeinterface in the DOM Core provides an interface to the list of entities that are defined for the document, and little else because the effect of namespaces and the various XML schema efforts on DTD representation are not clearly understood as of this writing.

DOM Level 3 doesn't support editingDocumentTypenodes.DocumentTypenodes areread-only.

The name of DTD; i.e., the name immediately following theDOCTYPEkeyword.

ANamedNodeMapcontaining the general entities, both external and internal, declared in the DTD. Parameter entities are not contained. Duplicates are discarded. For example in:<!DOCTYPE ex SYSTEM "ex.dtd" [ <!ENTITY foo "foo"> <!ENTITY bar "bar"> <!ENTITY bar "bar2"> <!ENTITY % baz "baz"> ]> <ex/>the interface provides access tofooand the first declaration ofbarbut not the second declaration ofbarorbaz. Every node in this map also implements theEntityinterface.

The DOM Level 2 does not support editing entities, thereforeentitiescannot be altered in any way.

ANamedNodeMapcontaining the notations declared in the DTD. Duplicates are discarded. Every node in this map also implements theNotationinterface.

The DOM Level 2 does not support editing notations, thereforenotationscannot be altered in any way.

The public identifier of the external subset.

The system identifier of the external subset. This may be an absolute URI or not.

The internal subset as a string, ornullif there is none. This is does not contain the delimiting square brackets.

The actual content returned depends on how much information is available to the implementation. This may vary depending on various parameters, including the XML processor used to build the document.

This interface represents a notation declared in the DTD. A notation either declares, by name, the format of an unparsed entity (seesection 4.7of the XML 1.0 specification), or is used for formal declaration of processing instruction targets (seesection 2.6of the XML 1.0 specification). ThenodeNameattribute inherited fromNodeis set to the declared name of the notation.

The DOM Core does not support editingNotationnodes; they are thereforereadonly.

ANotationnode does not have any parent.

The public identifier of this notation. If the public identifier was not specified, this isnull.

The system identifier of this notation. If the system identifier was not specified, this isnull. This may be an absolute URI or not.

This interface represents a known entity, either parsed or unparsed, in an XML document. Note that this models the entity itselfnotthe entity declaration.

ThenodeNameattribute that is inherited fromNodecontains the name of the entity.

An XML processor may choose to completely expand entities before the structure model is passed to the DOM; in this case there will be noEntityReferencenodes in the document tree.

XML does not mandate that a non-validating XML processor read and process entity declarations made in the external subset or declared in parameter entities. This means that parsed entities declared in the external subset need not be expanded by some classes of applications, and that the replacement text of the entity may not be available. When thereplacement textis available, the correspondingEntitynode's child list represents the structure of that replacement value. Otherwise, the child list is empty.

DOM Level 3 does not support editingEntitynodes; if a user wants to make changes to the contents of anEntity, every relatedEntityReferencenode has to be replaced in the structure model by a clone of theEntity's contents, and then the desired changes must be made to each of those clones instead.Entitynodes and all theirdescendantsarereadonly.

AnEntitynode does not have any parent.

If the entity contains an unboundnamespace prefix, thenamespaceURIof the corresponding node in theEntitynode subtree isnull. The same is true forEntityReferencenodes that refer to this entity, when they are created using thecreateEntityReferencemethod of theDocumentinterface.

The public identifier associated with the entity if specified, andnullotherwise.

The system identifier associated with the entity if specified, andnullotherwise. This may be an absolute URI or not.

For unparsed entities, the name of the notation for the entity. For parsed entities, this isnull.

An attribute specifying the encoding used for this entity at the time of parsing, when it is an external parsed entity. This isnullif it an entity from the internal subset or if it is not known.

An attribute specifying, as part of the text declaration, the encoding of this entity, when it is an external parsed entity. This isnullotherwise.

An attribute specifying, as part of the text declaration, the version number of this entity, when it is an external parsed entity. This isnullotherwise.

EntityReferencenodes may be used to represent an entity reference in the tree. Note that character references and references to predefined entities are considered to be expanded by the HTML or XML processor so that characters are represented by their Unicode equivalent rather than by an entity reference. Moreover, the XML processor may completely expand references to entities while building theDocument, instead of providingEntityReferencenodes. If it does provide such nodes, then for anEntityReferencenode that represents a reference to a known entity anEntityexists, and the subtree of theEntityReferencenode is a copy of theEntitynode subtree. However, the latter may not be true when an entity contains an unboundnamespace prefix. In such a case, because the namespace prefix resolution depends on where the entity reference is, thedescendantsof theEntityReferencenode may be bound to differentnamespace URIs. When anEntityReferencenode represents a reference to an unknown entity, the node has no children and its replacement value, when used byAttr.valuefor example, is empty.

As forEntitynodes,EntityReferencenodes and all theirdescendantsarereadonly.

EntityReferencenodes may cause element content and attribute value normalization problems when, such as in XML 1.0 and XML Schema, the normalization is performed after entity reference are expanded.

TheProcessingInstructioninterface represents a "processing instruction", used in XML as a way to keep processor-specific information in the text of the document.

No lexical check is done on the content of a processing instruction and it is therefore possible to have the character sequence"?>"in the content, which is illegal a processing instruction per section 2.6 of. The presence of this character sequence must generate a fatal error during serialization.

The target of this processing instruction. XML defines this as being the firsttokenfollowing the markup that begins the processing instruction.

The content of this processing instruction. This is from the first non white space character after the target to the character immediately preceding the?>.

NO_MODIFICATION_ALLOWED_ERR: Raised when the node is readonly.

Extensions to a language's native String class or interface

Returns the UTF-16 offset that corresponds to a UTF-32 offset. Used for random access.

You can always round-trip from a UTF-32 offset to a UTF-16 offset and back. You can round-trip from a UTF-16 offset to a UTF-32 offset and back if and only if the offset16 is not in the middle of a surrogate pair. Unmatched surrogates count as a single UTF-16 value.

UTF-32 offset.

UTF-16 offset

ifoffset32is out of bounds.

Returns the UTF-32 offset corresponding to a UTF-16 offset. Used for random access. To find the UTF-32 length of a string, use:len32 = findOffset32(source, source.length());

If the UTF-16 offset is into the middle of a surrogate pair, then the UTF-32 offset of theendof the pair is returned; that is, the index of the char after the end of the pair. You can always round-trip from a UTF-32 offset to a UTF-16 offset and back. You can round-trip from a UTF-16 offset to a UTF-32 offset and back if and only if the offset16 is not in the middle of a surrogate pair. Unmatched surrogates count as a single UTF-16 value.

UTF-16 offset

UTF-32 offset

if offset16 is out of bounds.