The Attr interface represents an attribute in an Element object.
CDATA sections are used to escape blocks of text containing characters that would otherwise be regarded as markup.
The CharacterData interface extends Node with a set of attributes and methods for accessing character data in the DOM.
This represents the content of a comment, i.e., all the characters between the starting ''.
The DOMConfiguration interface represents the configuration of a document and maintains a table of recognized parameters.
The Document interface represents the entire HTML or XML document.
DocumentFragment is a "lightweight" or "minimal" Document object.
Each Document has a doctype attribute whose value is either null or a DocumentType object.
The Element interface represents an element in an HTML or XML document.
This interface represents an entity, either parsed or unparsed, in an XML document.
EntityReference objects may be inserted into the structure model when an entity reference is in the source document, or when the user wishes to insert an entity reference.
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).
The DOMImplementation interface provides a number of methods for performing operations that are independent of any particular instance of the document object model.
Objects implementing the NamedNodeMap interface are used to represent collections of nodes that can be accessed by name.
The Node interface is the primary datatype for the entire Document Object Model.
The NodeList interface provides the abstraction of an ordered collection of nodes, without defining or constraining how this collection is implemented.
This interface represents a notation declared in the DTD.
The ProcessingInstruction interface represents a "processing instruction", used in XML as a way to keep processor-specific information in the text of the document.
The DOMStringList interface provides the abstraction of an ordered collection of DOMString values, without defining or constraining how this collection is implemented.
The Text interface inherits from CharacterData and represents the textual content (termed character data in XML) of an Element or Attr.
The Touch interface represents a single contact point on a touch-sensitive device.
The TouchList interface represents a list of contact points with a touch surface
Copyright © 2009-2017 Aarhus University