| | Interface | Description |
|---|
| | DOMConfiguration DOM 3 Core |
Used by Document.normalizeDocument(), and DOM Level 3 DOMParser() and DOMSerializer. |
| | DOMErrorHandler DOM 3 Core |
DOMErrorHandler is a callback interface that the DOM implementation can
call when reporting errors that happens while processing XML data, or
when doing some other processing (e.g. |
| | DOMException DOM 1 Core |
DOM operations only raise exceptions in "exceptional" circumstances. |
| | DOMImplementation DOM 1 Core |
The DOMImplementation interface provides a number of methods for
performing operations that are independent of any particular
instance of the document object model. |
| | DOMImplementationList DOM 3 Core |
Returned by DOMImplementationSource.getDOMImplementationList() and
DOMImplementationRegistry.getDOMImplementationList(). |
| | DOMImplementationRegistry DOM 3 Core |
This is a global variable used to get a single DOMImplementation or DOMImplementationList
depending on the registered objects with the specified features. |
| | DOMImplementationSource DOM 3 Core |
This interface permits a DOM implementer to supply one or more
implementations, based upon requested features and versions, as specified
in DOM Features. |
| | DOMLocator DOM 3 Core |
Indicates a location such as where an error occurred. |
| | DOMStringList DOM 3 Core |
The DOMStringList interface provides the abstraction of an ordered
collection of DOMString values, without defining or constraining how
this collection is implemented. |
| | NamedNodeMap DOM 1 Core |
Objects implementing the NamedNodeMap interface are used to represent
collections of nodes that can be accessed by name. |
| | NameList DOM 3 Core |
The NameList interface provides the abstraction of an ordered collection
of parallel pairs of name and namespace values (which could be null
values), without defining or constraining how this collection is
implemented. |
| | NodeList DOM 1 Core |
The NodeList interface provides the abstraction of an ordered collection
of nodes, without defining or constraining how this collection is
implemented. |
| | Class | Description |
|---|
| | Attr DOM 1 Core |
This type represents a DOM element's attribute as an object. |
| | CDATASection DOM 1 Core |
A CDATA Section can be used within XML to include extended portions of
unescaped text, such that the symbols < and & do not need escaping as
they normally do within XML when used as text. |
| | CharacterData DOM 1 Core |
Provides text manipulation methods that are used by several objects. |
| | Comment DOM 1 Core |
A comment is used to add notations within markup. |
| | Document DOM 0 |
In the DOM, the document object provides a general way to represent HTML,
XHTML, and XML documents. |
| | DocumentFragment DOM 1 Core |
A DocumentFragment is a minimal document object that has no parent. |
| | DocumentType DOM 1 Core |
Each Document has a doctype attribute whose value is either null or a
DocumentType object. |
| | DOMError DOM 3 Core |
DOMError is an interface that describes an error. |
| | Element |
The Element interface represents an element in an HTML or XML document. |
| | Entity DOM 1 Core |
This interface represents a known entity, either parsed or unparsed, in
an XML document. |
| | EntityReference DOM 1 Core |
Read-only reference to an entity reference in the DOM tree. |
| | ExceptionCode DOM 1 Core |
An integer indicating the type of error generated. |
| | Node DOM 1 Core |
A Node is an interface from which a number of DOM types inherit, and
allows these various types to be treated (or tested) similarly. |
| | Notation DOM 1 Core |
This interface represents a notation declared in the DTD. |
| | ProcessingInstruction DOM 1 Core |
A processing instruction provides an opportunity for application-specific
instructions to be embedded within XML and which can be ignored by XML
processors which do not support processing their instructions (outside of
their having a place in the DOM). |
| | Text DOM 1 Core |
The Text interface represents the textual content of an Element or Attr. |
| | TypeInfo DOM 3 Core |
The TypeInfo interface represents a type referenced from Element or Attr
nodes, specified in the schemas associated with the document. |
| | UserDataHandler DOM 3 Core |
When associating user data with a key on a node, Node.setUserData()
can also accept, in its third argument, a handler which will be
called when the object is cloned, imported, deleted, renamed, or
adopted. |
