This section defines a set of objects and interfaces for
accessing and manipulating document objects. The functionality
specified in this section (the Core functionality) is
sufficient to allow software developers and web script authors to
access and manipulate parsed HTML and XML content inside conforming
products. The DOM Core API also allows creation and
population of a Document object using only
DOM API calls; loading a Document and saving it
persistently is left to the product that implements the DOM
API.
The DOM presents documents as a hierarchy of Node objects that also
implement other, more specialized interfaces. Some types of nodes
may have child nodes
of various types, and others are leaf nodes that cannot have
anything below them in the document structure. For XML and HTML,
the node types, and which node types they may have as children, are
as follows:
Document -- Element (maximum of
one), ProcessingInstruction,
Comment, DocumentType
(maximum of one)DocumentFragment -- Element, ProcessingInstruction,
Comment, Text, CDATASection, EntityReferenceDocumentType
-- no childrenEntityReference -- Element, ProcessingInstruction,
Comment, Text, CDATASection, EntityReferenceElement -- Element, Text, Comment, ProcessingInstruction,
CDATASection, EntityReferenceAttr -- Text, EntityReferenceProcessingInstruction --
no childrenComment --
no childrenText -- no
childrenCDATASection
-- no childrenEntity -- Element, ProcessingInstruction,
Comment, Text, CDATASection, EntityReferenceNotation -- no
childrenThe DOM also specifies a NodeList interface to
handle ordered lists of Nodes, such as the
children of a Node, or the elements returned by the
getElementsByTagName method of the Element interface, and
also a NamedNodeMap interface
to handle unordered sets of nodes referenced by their name
attribute, such as the attributes of an Element. NodeList and NamedNodeMap objects in
the DOM are live; that is, changes to the underlying
document structure are reflected in all relevant NodeList and NamedNodeMap objects.
For example, if a DOM user gets a NodeList object
containing the children of an Element, then
subsequently adds more children to that element (or removes
children, or modifies them), those changes are automatically
reflected in the NodeList, without further
action on the user's part. Likewise, changes to a Node in the tree are
reflected in all references to that Node in NodeList
and NamedNodeMap
objects.
Finally, the interfaces Text, Comment, and CDATASection all inherit
from the CharacterData
interface.
Most of the APIs defined by this specification are
interfaces rather than classes. That means that an
implementation need only expose methods with the defined names and
specified operation, not implement classes that correspond directly
to the interfaces. This allows the DOM APIs to be implemented as a
thin veneer on top of legacy applications with their own data
structures, or on top of newer applications with different class
hierarchies. This also means that ordinary constructors (in the
Java or C++ sense) cannot be used to create DOM objects, since the
underlying objects to be constructed may have little relationship
to the DOM interfaces. The conventional solution to this in
object-oriented design is to define factory methods that
create instances of objects that implement the various interfaces.
Objects implementing some interface "X" are created by a
"createX()" method on the Document interface; this is
because all DOM objects live in the context of a specific
Document.
The Core DOM APIs are designed to be compatible with a wide range of languages, including both general-user scripting languages and the more challenging languages used mostly by professional programmers. Thus, the DOM APIs need to operate across a variety of memory management philosophies, from language bindings that do not expose memory management to the user at all, through those (notably Java) that provide explicit constructors but provide an automatic garbage collection mechanism to automatically reclaim unused memory, to those (especially C/C++) that generally require the programmer to explicitly allocate object memory, track where it is used, and explicitly free it for re-use. To ensure a consistent API across these platforms, the DOM does not address memory management issues at all, but instead leaves these for the implementation. Neither of the explicit language bindings defined by the DOM API (for ECMAScript and Java) require any memory management methods, but DOM bindings for other languages (especially C or C++) may require such support. These extensions will be the responsibility of those adapting the DOM API to a specific language, not the DOM Working Group.
While it would be nice to have attribute and method names that
are short, informative, internally consistent, and familiar to
users of similar APIs, the names also should not clash with the
names in legacy APIs supported by DOM implementations. Furthermore,
both OMG IDL and ECMAScript have significant
limitations in their ability to disambiguate names from different
namespaces that make it difficult to avoid naming conflicts with
short, familiar names. So, DOM names tend to be long and
descriptive in order to be unique across all environments.
The Working Group has also attempted to be internally consistent in its use of various terms, even though these may not be common distinctions in other APIs. For example, the DOM API uses the method name "remove" when the method changes the structural model, and the method name "delete" when the method gets rid of something inside the structure model. The thing that is deleted is not returned. The thing that is removed may be returned, when it makes sense to return it.
The DOM Core APIs
present two somewhat different sets of interfaces to an XML/HTML
document: one presenting an "object oriented" approach with a
hierarchy of inheritance, and a
"simplified" view that allows all manipulation to be done via the
Node interface
without requiring casts (in Java and other C-like languages) or
query interface calls in COM environments. These
operations are fairly expensive in Java and COM, and the DOM may be
used in performance-critical environments, so we allow significant
functionality using just the Node interface. Because
many other users will find the inheritance hierarchy
easier to understand than the "everything is a Node" approach to
the DOM, we also support the full higher-level interfaces for those
who prefer a more object-oriented API.
In practice, this means that there is a certain amount of
redundancy in the API.
The Working Group considers the "inheritance" approach
the primary view of the API, and the full set of functionality on
Node to be
"extra" functionality that users may employ, but that does not
eliminate the need for methods on other interfaces that an
object-oriented analysis would dictate. (Of course, when the O-O
analysis yields an attribute or method that is identical to one on
the Node interface, we don't
specify a completely redundant one.) Thus, even though there is a
generic nodeName attribute on the Node interface,
there is still a tagName attribute on the Element interface; these
two attributes must contain the same value, but the it is
worthwhile to support both, given the different constituencies the
DOM API must
satisfy.
DOMString typeTo ensure interoperability, the DOM specifies the following:
A DOMString is a
sequence of 16-bit
units.
valuetype DOMString sequence<unsigned short>;
Applications must encode DOMString using UTF-16
(defined in [Unicode 2.0] and Amendment 1 of [ISO/IEC
10646]).
The UTF-16 encoding was chosen because of its widespread
industry practice. Note that for both HTML and XML, the document
character set (and therefore the notation of numeric character
references) is based on UCS [ISO/IEC 10646]. A single numeric
character reference in a source document may therefore in some
cases correspond to two 16-bit units in a DOMString (a high surrogate
and a low surrogate).
Note: Even though the DOM defines the name of the string
type to be DOMString, bindings may use
different names. For example for Java, DOMString is bound to the
String type because it also uses UTF-16 as its
encoding.
Note: As of August 2000, the OMG IDL specification ([OMG
IDL]) included a wstring type. However, that
definition did not meet the interoperability criteria of the DOM API since it relied on
negotiation to decide the width and encoding of a character.
DOMTimeStamp typeTo ensure interoperability, the DOM specifies the following:
A DOMTimeStamp
represents a number of milliseconds.
typedef unsigned long long DOMTimeStamp;
Note: Even though the DOM uses the type DOMTimeStamp, bindings
may use different types. For example for Java, DOMTimeStamp is
bound to the long type. In ECMAScript,
TimeStamp is bound to the Date type
because the range of the integer type is too
small.
DOMUserData typeTo ensure interoperability, the DOM specifies the following:
A DOMUserData
represents a reference to an application object.
typedef Object DOMUserData;
Note: Even though the DOM uses the type DOMUserData, bindings may
use different types. For example, in Java DOMUserData is bound to
the Object type, while in ECMAScript DOMUserData is bound
to any type.
DOMObject typeTo ensure interoperability, the DOM specifies the following:
A DOMObject
represents a reference to an application object.
typedef Object DOMObject;
Note: Even though the DOM uses the type DOMObject, bindings may use
different types. For example, in Java and ECMAScript DOMObject is
bound to the Object type.
The DOM has many interfaces that imply string matching. HTML
processors generally assume an uppercase (less often, lowercase)
normalization of names for such things as elements, while XML is
explicitly case sensitive. For the purposes of the DOM, string
matching is performed purely by binary comparison of the 16-bit units of
the DOMString. In
addition, the DOM assumes that any case normalizations take place
in the processor, before the DOM structures are built.
The W3C Text normalization, as defined in [CharModel],
is assumed to happen at serialization time. The DOM Level 3 Load
and Save module [DOM Level 3 Abstract Schemas and Load and
Save] provides a serialization mechanism (see the
DOMWriter interface, section 2.3.1) and defines the
"ls-normalize-characters" to assure that text is
serialized in the W3C Text Normalization form. Other serialization
mechanisms built on top of the DOM Level 3 Core also have to assure
that text is serialized in the W3C Text Normalization form.
The DOM Level 2 (and higher) supports XML namespaces [XML Namespaces] by augmenting several interfaces of the DOM Level 1 Core to allow creating and manipulating elements and attributes associated to a namespace.
As far as the DOM is concerned, special attributes used for declaring XML namespaces are still exposed and can be manipulated just like any other attribute. However, nodes are permanently bound to namespace URIs as they get created. Consequently, moving a node within a document, using the DOM, in no case results in a change of its namespace prefix or namespace URI. Similarly, creating a node with a namespace prefix and namespace URI, or changing the namespace prefix of a node, does not result in any addition, removal, or modification of any special attributes for declaring the appropriate XML namespaces. Namespace validation is not enforced; the DOM application is responsible. In particular, since the mapping between prefixes and namespace URIs is not enforced, in general, the resulting document cannot be serialized naively. For example, applications may have to declare every namespace in use when serializing a document.
In general, the DOM implementation (and higher) doesn't perform
any URI normalization or canonicalization. The URIs given to the
DOM are assumed to be valid (e.g., characters such as white spaces
are properly escaped), and no lexical checking is performed.
Absolute URI references are treated as strings and compared literally.
How relative namespace URI references are treated is undefined. To
ensure interoperability only absolute namespace URI references
(i.e., URI references beginning with a scheme name and a colon)
should be used. Applications that wish to have no namespace should
use the value null as the namespaceURI parameter of
methods. If they pass an empty string the DOM implementation turns
it into a null.
Note: In the DOM, all namespace declaration attributes are by definition bound to the namespace URI: "http://www.w3.org/2000/xmlns/". These are the attributes whose namespace prefix or qualified name is "xmlns". Although, at the time of writing, this is not part of the XML Namespaces specification [XML Namespaces], it is planned to be incorporated in a future revision.
In a document with no namespaces, the child list of an EntityReference node is
always the same as that of the corresponding Entity. This is not true
in a document where an entity contains unbound namespace prefixes.
In such a case, the descendants of the
corresponding EntityReference nodes may
be bound to different namespace URIs,
depending on where the entity references are. Also, because, in the
DOM, nodes always remain bound to the same namespace URI, moving
such EntityReference nodes can
lead to documents that cannot be serialized. This is also true when
the DOM Level 1 method createEntityReference of the Document interface is
used to create entity references that correspond to such entities,
since the descendants of the
returned EntityReference are
unbound. The DOM Level 2 does not support any mechanism to resolve
namespace prefixes. For all of these reasons, use of such entities
and entity references should be avoided or used with extreme care.
A future Level of the DOM may include some additional support for
handling these.
The new methods, such as createElementNS and
createAttributeNS of the Document interface, are
meant to be used by namespace aware applications. Simple
applications that do not use namespaces can use the DOM Level 1
methods, such as createElement and
createAttribute. Elements and attributes created in
this way do not have any namespace prefix, namespace URI, or local
name.
Note: Given that the property [in-scope namespaces] defined in [XML Information set] is not accessible from DOM Level 3 Core, the properties [prefix] and [namespace name] defined by the Namespace Information Item in [XML Information set] are not accessible from DOM Level 3 Core. However, [DOM Level 3 XPath] does provide a way to access them.
Note: DOM Level 1 methods are namespace ignorant.
Therefore, while it is safe to use these methods when not dealing
with namespaces, using them and the new ones at the same time
should be avoided. DOM Level 1 methods solely identify attribute
nodes by their nodeName. On the contrary, the DOM
Level 2 methods related to namespaces, identify attribute nodes by
their namespaceURI and localName. Because
of this fundamental difference, mixing both sets of methods can
lead to unpredictable results. In particular, using
setAttributeNS, an element may have two
attributes (or more) that have the same nodeName, but
different namespaceURIs. Calling
getAttribute with that nodeName could
then return any of those attributes. The result depends on the
implementation. Similarly, using setAttributeNode, one
can set two attributes (or more) that have different
nodeNames but the same prefix and
namespaceURI. In this case
getAttributeNodeNS will return either attribute, in an
implementation dependent manner. The only guarantee in such cases
is that all methods that access a named item by its
nodeName will access the same item, and all methods
which access a node by its URI and local name will access the same
node. For instance, setAttribute and
setAttributeNS affect the node that
getAttribute and getAttributeNS,
respectively, return.
As new XML vocabularies are developed, those defining the vocabularies are also beginning to define specialized APIs for manipulating XML instances of those vocabularies. This is usually done by extending the DOM to provide interfaces and methods that perform operations frequently needed their users. For example, the MathML [MathML 2.0] and SVG [SVG 1.0] specifications are developing DOM extensions to allow users to manipulate instances of these vocabularies using semantics appropriate to images and mathematics (respectively) as well as the generic DOM XML semantics. Instances of SVG or MathML are often embedded in XML documents conforming to a different schema such as XHTML.
While the XML Namespaces Recommendation provides a mechanism for integrating these documents at the syntax level, it has become clear that the DOM Level 2 Recommendation [DOM Level 2 Core] is not rich enough to cover all the issues that have been encountered in having these different DOM implementations be used together in a single application. DOM Level 3 deals with the requirements brought about by embedding fragments written according to a specific markup language (the embedded component) in a document where the rest of the markup is not written according to that specific markup language (the host document). It does not deal with fragments embedded by reference or linking.
A DOM implementation supporting DOM Level 3 Core should be able to collaborate with subcomponents implementing specific DOMs to assemble a compound document that can be traversed and manipulated via DOM interfaces as if it were a seamless whole.
The normal typecast operation on an object should support the
interfaces expected by legacy code for a given document type.
Typecasting techniques may not be adequate for selecting between
multiple DOM specializations of an object which were combined at
run time, because they may not all be part of the same object as
defined by the binding's object model. Conflicts are most obvious
with the Document
object, since it is shared as owner by the rest of the document. In
a homogeneous document, elements rely on the Document for
specialized services and construction of specialized nodes. In a
heterogeneous document, elements from different modules expect
different services and APIs from the same Document object, since
there can only be one owner and root of the document hierarchy.
Because previous versions of the DOM specification only defined a set of interfaces, applications had to rely on some implementation dependent code to start from. However, hard-coding the application to a specific implementation prevents the application from running on other implementations and from using the most-suitable implementation of the environment. At the same time, implementations may also need to load modules or perform other setup to efficiently adapt to different and sometimes mutually-exclusive feature sets.
To solve these problems this specification introduces a
DOMImplementationRegistry object with a function that
lets an application find an implementation, based on the specific
features it requires. How this object is found and what it exactly
looks like is not defined here, because this cannot be done in a
language-independent manner. Instead, each language binding defines
its own way of doing this. See Java Language Binding and ECMAScript Language
Binding for specifics.
In all cases, though, the DOMImplementationRegistry
provides a getDOMImplementation method accepting a
features string, which is passed to every known DOMImplementationSource
until a suitable DOMImplementation is
found and returned. This method is the same as the one found on the
DOMImplementationSource
interface defined below.
Any number of DOMImplementationSource
objects can be registered. A source may return one or more DOMImplementation
singletons or construct new DOMImplementation
objects, depending upon whether the requested features require
specialized state in the DOMImplementation
object.
getDOMImplementation be called
byFeature instead?The interfaces within this section are considered fundamental, and must be fully implemented by all conforming implementations of the DOM, including all HTML DOM implementations [DOM Level 2 HTML], unless otherwise specified.
A DOM application may use the hasFeature(feature,
version) method of the DOMImplementation
interface with parameter values "Core" and "3.0" (respectively) to
determine whether or not this module is supported by the
implementation. Any implementation that conforms to DOM Level 3 or
a DOM Level 3 module must conform to the Core module. Please refer
to additional information about
conformance in this specification. The DOM Level 3
Core module is backward compatible with the DOM Level 2 Core [DOM Level
2 Core] module, i.e. a DOM Level 3 Core implementation who
returns true for "Core" with the version
number "3.0" must also return true for
this feature when the version number is
"2.0", "" or, null.
DOM operations only raise exceptions in "exceptional"
circumstances, i.e., when an operation is impossible to perform
(either for logical reasons, because data is lost, or because the
implementation has become unstable). In general, DOM methods return
specific error values in ordinary processing situations, such as
out-of-bound errors when using NodeList.
Implementations should raise other exceptions under other
circumstances. For example, implementations should raise an
implementation-dependent exception if a null argument
is passed when null was not expected.
Some languages and object systems do not support the concept of exceptions. For such systems, error conditions may be indicated using native error reporting mechanisms. For some bindings, for example, methods may return error codes similar to those listed in the corresponding method descriptions.
exception DOMException { unsigned short code; }; // ExceptionCode const unsigned short INDEX_SIZE_ERR = 1; const unsigned short DOMSTRING_SIZE_ERR = 2; const unsigned short HIERARCHY_REQUEST_ERR = 3; const unsigned short WRONG_DOCUMENT_ERR = 4; const unsigned short INVALID_CHARACTER_ERR = 5; const unsigned short NO_DATA_ALLOWED_ERR = 6; const unsigned short NO_MODIFICATION_ALLOWED_ERR = 7; const unsigned short NOT_FOUND_ERR = 8; const unsigned short NOT_SUPPORTED_ERR = 9; const unsigned short INUSE_ATTRIBUTE_ERR = 10; // Introduced in DOM Level 2: const unsigned short INVALID_STATE_ERR = 11; // Introduced in DOM Level 2: const unsigned short SYNTAX_ERR = 12; // Introduced in DOM Level 2: const unsigned short INVALID_MODIFICATION_ERR = 13; // Introduced in DOM Level 2: const unsigned short NAMESPACE_ERR = 14; // Introduced in DOM Level 2: const unsigned short INVALID_ACCESS_ERR = 15; // Introduced in DOM Level 3: const unsigned short VALIDATION_ERR = 16;
An integer indicating the type of error generated.
Note: Other numeric codes are reserved for W3C for possible future use.
DOMSTRING_SIZE_ERRHIERARCHY_REQUEST_ERRINDEX_SIZE_ERRINUSE_ATTRIBUTE_ERRINVALID_ACCESS_ERR, introduced in DOM Level 2.INVALID_CHARACTER_ERRINVALID_MODIFICATION_ERR, introduced in
DOM Level 2.INVALID_STATE_ERR, introduced in DOM Level 2.NAMESPACE_ERR, introduced in DOM Level 2.NOT_FOUND_ERRNOT_SUPPORTED_ERRNO_DATA_ALLOWED_ERRNO_MODIFICATION_ALLOWED_ERRSYNTAX_ERR, introduced in DOM Level 2.VALIDATION_ERR, introduced in DOM Level 3.insertBefore or
removeChild would make the Node invalid with
respect to "partial
validity", this exception would be raised and the
operation would not be done. This code is used in [DOM Level 3
Abstract Schemas and Load and Save]. Refer to this
specification for further information.WRONG_DOCUMENT_ERRThis interface permits a DOM implementer to supply one or more
implementations, based upon requested features. Each implemented
DOMImplementationSource object is listed in the
binding-specific list of available sources so that its DOMImplementation objects
are made available.
interface DOMImplementationSource { DOMImplementation getDOMImplementation(in DOMString features); };
getDOMImplementationfeatures of type DOMString|
An implementation that has the desired features, or
|
The DOMImplementation interface provides a number
of methods for performing operations that are independent of any
particular instance of the document object model.
interface DOMImplementation { boolean hasFeature(in DOMString feature, in DOMString version); // Introduced in DOM Level 2: DocumentType createDocumentType(in DOMString qualifiedName, in DOMString publicId, in DOMString systemId) raises(DOMException); // Introduced in DOM Level 2: Document createDocument(in DOMString namespaceURI, in DOMString qualifiedName, in DocumentType doctype) raises(DOMException); // Introduced in DOM Level 3: DOMImplementation getInterface(in DOMString feature); };
createDocument
introduced in DOM Level 2DocumentType given to
create the document, the implementation may instantiate specialized
Document objects
that support additional features than the "Core", such as "HTML"
[DOM
Level 2 HTML]. On the other hand, setting the DocumentType after
the document was created makes this very unlikely to happen.
Alternatively, specialized Document creation methods,
such as createHTMLDocument [DOM Level 2
HTML], can be used to obtain specific types of Document
objects.
namespaceURI of type DOMStringnull.qualifiedName of type DOMStringnull.doctype of type DocumentTypenull.doctype is not null, its Node.ownerDocument
attribute is set to the document being created.|
INVALID_CHARACTER_ERR: Raised if the specified qualified name contains an illegal character. NAMESPACE_ERR: Raised if the WRONG_DOCUMENT_ERR: Raised if NOT_SUPPORTED_ERR: May be raised by DOM implementations which do not support the "XML" feature, if they choose not to support this method. Note: Other features introduced in the future, by the DOM WG or in extensions defined by other groups, may also demand support for this method; please consult the definition of the feature to see if it requires this method. |
createDocumentType
introduced in DOM Level 2DocumentType node. Entity
declarations and notations are not made available. Entity reference
expansions and default attribute additions do not occur. It is
expected that a future version of the DOM will provide a way for
populating a DocumentType.
qualifiedName of type DOMStringpublicId of type DOMStringsystemId of type DOMString|
A new |
|
INVALID_CHARACTER_ERR: Raised if the specified qualified name contains an illegal character. NAMESPACE_ERR: Raised if the NOT_SUPPORTED_ERR: May be raised by DOM implementations which do
not support the Note: Other features introduced in the future, by the DOM WG or in extensions defined by other groups, may also demand support for this method; please consult the definition of the feature to see if it requires this method. |
getInterface
introduced in DOM Level 3DOMImplementation's specialized interface (see Mixed DOM implementations).
feature of type DOMString|
Returns an alternate |
hasFeaturefeature of type DOMStringversion of type DOMStringnull or empty string, supporting any version of the
feature causes the method to return true.|
|
|
DocumentFragment is a "lightweight" or "minimal" Document object. It is
very common to want to be able to extract a portion of a document's
tree or to create a new fragment of a document. Imagine
implementing a user command like cut or rearranging a document by
moving fragments around. It is desirable to have an object which
can hold such fragments and it is quite natural to use a Node for
this purpose. While it is true that a Document object could
fulfill this role, a Document object can
potentially be a heavyweight object, depending on the underlying
implementation. What is really needed for this is a very
lightweight object. DocumentFragment is such an
object.
Furthermore, various operations -- such as inserting nodes as
children of another Node -- may take
DocumentFragment objects as arguments; this results in
all the child nodes of the DocumentFragment being
moved to the child list of this node.
The children of a DocumentFragment node are zero or
more nodes representing the tops of any sub-trees defining the
structure of the document. DocumentFragment nodes do
not need to be well-formed XML
documents (although they do need to follow the rules
imposed upon well-formed XML parsed entities, which can have
multiple top nodes). For example, a DocumentFragment
might have only one child and that child node could be a Text node. Such a
structure model represents neither an HTML document nor a
well-formed XML document.
When a DocumentFragment is inserted into a Document (or indeed any
other Node that
may take children) the children of the
DocumentFragment and not the
DocumentFragment itself are inserted into the Node. This makes the
DocumentFragment very useful when the user wishes to
create nodes that are siblings; the
DocumentFragment acts as the parent of these nodes so
that the user can use the standard methods from the Node
interface, such as insertBefore and
appendChild.
Note: The properties [notations] and [unparsed entities]
defined by the Document Information Item in [XML Information
set] are accessible through the DocumentType interface.
The property [all declarations processed] is not accessible through
the DOM API.
interface DocumentFragment : Node { };
The Document interface represents the entire HTML
or XML document. Conceptually, it is the root of the document
tree, and provides the primary access to the document's data.
Since elements, text nodes, comments, processing instructions,
etc. cannot exist outside the context of a Document,
the Document interface also contains the factory
methods needed to create these objects. The Node objects created
have a ownerDocument attribute which associates them
with the Document within whose context they were
created.
interface Document : Node { // Modified in DOM Level 3: readonly attribute DocumentType doctype; readonly attribute DOMImplementation implementation; readonly attribute Element documentElement; Element createElement(in DOMString tagName) raises(DOMException); DocumentFragment createDocumentFragment(); Text createTextNode(in DOMString data); Comment createComment(in DOMString data); CDATASection createCDATASection(in DOMString data) raises(DOMException); ProcessingInstruction createProcessingInstruction(in DOMString target, in DOMString data) raises(DOMException); Attr createAttribute(in DOMString name) raises(DOMException); EntityReference createEntityReference(in DOMString name) raises(DOMException); NodeList getElementsByTagName(in DOMString tagname); // Introduced in DOM Level 2: Node importNode(in Node importedNode, in boolean deep) raises(DOMException); // Introduced in DOM Level 2: Element createElementNS(in DOMString namespaceURI, in DOMString qualifiedName) raises(DOMException); // Introduced in DOM Level 2: Attr createAttributeNS(in DOMString namespaceURI, in DOMString qualifiedName) raises(DOMException); // Introduced in DOM Level 2: NodeList getElementsByTagNameNS(in DOMString namespaceURI, in DOMString localName); // Introduced in DOM Level 2: Element getElementById(in DOMString elementId); // Introduced in DOM Level 3: attribute DOMString actualEncoding; // Introduced in DOM Level 3: attribute DOMString encoding; // Introduced in DOM Level 3: attribute boolean standalone; // Introduced in DOM Level 3: attribute DOMString version; // raises(DOMException) on setting // Introduced in DOM Level 3: attribute boolean strictErrorChecking; // Introduced in DOM Level 3: attribute DOMErrorHandler errorHandler; // Introduced in DOM Level 3: attribute DOMString documentURI; // Introduced in DOM Level 3: Node adoptNode(in Node source) raises(DOMException); // Introduced in DOM Level 3: void normalizeDocument(); // Introduced in DOM Level 3: boolean canSetNormalizationFeature(in DOMString name, in boolean state); // Introduced in DOM Level 3: void setNormalizationFeature(in DOMString name, in boolean state) raises(DOMException); // Introduced in DOM Level 3: boolean getNormalizationFeature(in DOMString name) raises(DOMException); // Introduced in DOM Level 3: Node renameNode(in Node n, in DOMString namespaceURI, in DOMString name) raises(DOMException); };
actualEncoding of type
DOMString,
introduced in DOM Level 3null otherwise.doctype of type DocumentType, readonly,
modified in DOM Level 3DocumentType) associated
with this document. For HTML documents as well as XML documents
without a document type declaration this returns
null.DocumentType node, child
node of this Document. This node can be set at
document creation time and later changed through the use of child
nodes manipulation methods, such as insertBefore, or
replaceChild. Note, however, that while some
implementations may instantiate different types of
Document objects supporting additional features than
the "Core", such as "HTML" [DOM Level 2 HTML], based on the DocumentType specified at
creation time, changing it afterwards is very unlikely to result in
a change of the features supported.documentElement of type Element, readonlydocumentURI of type DOMString, introduced
in DOM Level 3null if
undefined.Document supports the feature
"HTML" [DOM Level 2 HTML], the href
attribute of the HTML BASE element takes precedence over this
attribute.encoding of type DOMString, introduced in DOM Level 3null when
unspecified.errorHandler of type DOMErrorHandler,
introduced in DOM Level 3DOMErrorHandler
to be called in the event that an error is encountered while
performing an operation on a document. Note that not all methods
use this mechanism, see the description of each method for
details.implementation of type DOMImplementation,
readonlyDOMImplementation object
that handles this document. A DOM application may use objects from
multiple implementations.standalone of type
boolean, introduced in DOM Level
3strictErrorChecking of
type boolean, introduced in DOM
Level 3false, the implementation is free to
not test every possible error case normally defined on DOM
operations, and not raise any DOMException. In case of
error, the behavior is undefined. This attribute is
true by defaults.version of type DOMString, introduced in DOM Level 3null when
unspecified.|
NOT_SUPPORTED_ERR: Raised if the version is set to a value that
is not supported by this |
adoptNode introduced in DOM Level 3ownerDocument of a
node, its children, as well as the attached attribute nodes if
there are any. If the node has a parent it is first removed from
its parent child list. This effectively allows moving a subtree
from one document to another. The following list describes the
specifics for each type of node.
ownerElement attribute is set to
null and the specified flag is set to
true on the adopted Attr. The descendants of
the source Attr are recursively
adopted.Document nodes cannot be adopted.DocumentType
nodes cannot be adopted.Attr nodes. Default
attributes are discarded, though if the document being adopted into
defines default attributes for this element name, those are
assigned. The descendants of the source element are recursively
adopted.Entity nodes
cannot be adopted.EntityReference node
itself is adopted, the descendants are discarded, since the source
and destination documents might have defined the entity
differently. If the document being imported into provides a
definition for this entity name, its value is assigned.Notation nodes
cannot be adopted.source of type Node|
The adopted node, or |
|
NOT_SUPPORTED_ERR: Raised if the source node is of type
NO_MODIFICATION_ALLOWED_ERR: Raised when the source node is readonly. |
canSetNormalizationFeature
introduced in DOM Level 3hasFeature
string.
name of type DOMStringstate of type
booleantrue or
false).|
|
|
createAttributeAttr of the given name.
Note that the Attr instance can then be
set on an Element
using the setAttributeNode method.createAttributeNS method.
name of type DOMString|
INVALID_CHARACTER_ERR: Raised if the specified name contains an illegal character. |
createAttributeNS introduced in DOM Level 2namespaceURI of type DOMStringqualifiedName of type DOMString|
A new
|
|
INVALID_CHARACTER_ERR: Raised if the specified qualified name contains an illegal character, per the XML 1.0 specification [XML 1.0]. NAMESPACE_ERR: Raised if the NOT_SUPPORTED_ERR: Always thrown if the current document does
not support the |
createCDATASectionCDATASection node whose
value is the specified string.
data of type DOMStringCDATASection
contents.|
The new |
|
NOT_SUPPORTED_ERR: Raised if this document is an HTML document. |
createCommentcreateDocumentFragmentDocumentFragment object.
|
A new |
createElementElement interface, so
attributes can be specified directly on the returned object.Attr nodes
representing them are automatically created and attached to the
element.createElementNS method.
tagName of type DOMString|
INVALID_CHARACTER_ERR: Raised if the specified name contains an illegal character. |
createElementNS introduced in DOM Level 2namespaceURI of type DOMStringqualifiedName of type DOMString|
A new
|
|
INVALID_CHARACTER_ERR: Raised if the specified qualified name contains an illegal character, per the XML 1.0 specification [XML 1.0]. NAMESPACE_ERR: Raised if the NOT_SUPPORTED_ERR: Always thrown if the current document does
not support the |
createEntityReferenceEntityReference object. In
addition, if the referenced entity is known, the child list of the
EntityReference node is
made the same as that of the corresponding Entity node.
Note: If any descendant of the Entity node has an unbound
namespace
prefix, the corresponding descendant of the created EntityReference node
is also unbound; (its namespaceURI is
null). The DOM Level 2 does not support any mechanism
to resolve namespace prefixes.
name of type DOMString|
The new |
|
INVALID_CHARACTER_ERR: Raised if the specified name contains an illegal character. NOT_SUPPORTED_ERR: Raised if this document is an HTML document. |
createProcessingInstructionProcessingInstruction
node given the specified name and data strings.
|
The new |
|
INVALID_CHARACTER_ERR: Raised if the specified target contains an illegal character. NOT_SUPPORTED_ERR: Raised if this document is an HTML document. |
createTextNodegetElementById introduced in DOM Level 2Element whose
ID is given by elementId. If no such
element exists, returns null. Behavior is not defined
if more than one element has this ID.
Note: The DOM implementation must have information that
says which attributes are of type ID. Attributes with the name "ID"
are not of type ID unless so defined. Implementations that do not
know whether attributes are of type ID or not are expected to
return null.
elementId of type DOMStringid value for an element.|
The matching element. |
getElementsByTagNameNodeList of all the Elements with a
given tag name in document order.
tagname of type DOMStringgetElementsByTagNameNS introduced in DOM Level 2NodeList of all the Elements with a
given local name
and namespace URI in document order.
namespaceURI of type DOMStringlocalName of type DOMStringgetNormalizationFeature
introduced in DOM Level 3hasFeature
string. The recognized features are the same as the ones defined
for setNormalizationFeature.
name of type DOMString|
|
The current state of the feature ( |
|
NOT_FOUND_ERR: Raised when the feature name is not recognized. |
importNode introduced in
DOM Level 2parentNode
is null). The source node is not altered or removed
from the original document; this method creates a new copy of the
source node.nodeName and nodeType, plus the
attributes related to namespaces (prefix,
localName, and namespaceURI). As in the
cloneNode operation, the source node is not altered.
User data associated to the imported node is not carried over.
However, if any UserDataHandlers has
been specified along with the associated data these handlers will
be called with the appropriate parameters before this method
returns.nodeType, attempting to mirror the behavior expected
if a fragment of XML or HTML source was copied from one document to
another, recognizing that the two documents may have different DTDs
in the XML case. The following list describes the specifics for
each type of node.
ownerElement attribute is set to
null and the specified flag is set to
true on the generated Attr. The descendants of the
source Attr are recursively
imported and the resulting nodes reassembled to form the
corresponding subtree.deep parameter has no effect on Attr nodes; they always
carry their children with them when imported.deep option was set to true,
the descendants
of the source DocumentFragment are
recursively imported and the resulting nodes reassembled under the
imported DocumentFragment to form
the corresponding subtree. Otherwise, this simply generates an
empty DocumentFragment.Document nodes cannot be imported.DocumentType
nodes cannot be imported.Attr nodes are attached
to the generated Element. Default
attributes are not copied, though if the document being
imported into defines default attributes for this element name,
those are assigned. If the importNode
deep parameter was set to true, the descendants of the
source element are recursively imported and the resulting nodes
reassembled to form the corresponding subtree.Entity nodes
can be imported, however in the current release of the DOM the DocumentType is
readonly. Ability to add these imported nodes to a DocumentType will be
considered for addition to a future release of the DOM.publicId, systemId, and
notationName attributes are copied. If a
deep import is requested, the descendants of the the
source Entity are
recursively imported and the resulting nodes reassembled to form
the corresponding subtree.EntityReference itself is
copied, even if a deep import is requested, since the
source and destination documents might have defined the entity
differently. If the document being imported into provides a
definition for this entity name, its value is assigned.Notation nodes
can be imported, however in the current release of the DOM the DocumentType is
readonly. Ability to add these imported nodes to a DocumentType will be
considered for addition to a future release of the DOM.publicId and systemId
attributes are copied.deep parameter has no effect on this
type of nodes since they cannot have any children.target and
data values from those of the source node.deep parameter has no effect on this
type of nodes since they cannot have any children.CharacterData copy their
data and length attributes from those of
the source node.deep parameter has no effect on these
types of nodes since they cannot have any children.importedNode of type Nodedeep of type
booleantrue, recursively import the subtree under the
specified node; if false, import only the node itself,
as explained above. This has no effect on nodes that cannot have
any children, and on Attr, and EntityReference
nodes.|
The imported node that belongs to this
|
|
NOT_SUPPORTED_ERR: Raised if the type of node being imported is not supported. INVALID_CHARACTER_ERR: Raised if one the imported names contain an illegal character. This may happen when importing an XML 1.1 [XML 1.1] element into an XML 1.0 document, for instance. |
normalizeDocument
introduced in DOM Level 3setNormalizationFeature for details.Text nodes, makes the
document "namespace wellformed", according to the algorithm
described below in pseudo code, by adding missing namespace
declaration attributes and adding or changing namespace prefixes,
updates the replacement tree of EntityReference nodes,
normalizes attribute values, etc.renameNode