Take the Node TextContent property as an example, both getTextContent and setTextContent shared the same content that defined the TextContent property itself.
| Class | Description | 
|---|---|
| Attr | The  Attrinterface represents an attribute in anElementobject. | 
| CDATASection | CDATA sections are used to escape blocks of text containing characters that would otherwise be regarded as markup. | 
| CharacterData | The  CharacterDatainterface extends Node with a set of attributes and methods for accessing character data in the DOM. | 
| Comment | This interface inherits from  CharacterDataand represents the content of a comment, i.e., all the characters between the starting '<!--' and ending '-->'. | 
| Document | The  Documentinterface represents the entire HTML or XML document. | 
| DocumentFragment | DocumentFragmentis a "lightweight" or "minimal"Documentobject. | 
| DocumentType | Each  Documenthas adoctypeattribute whose value is eithernullor aDocumentTypeobject. | 
| DOMConfiguration | The  DOMConfigurationinterface represents the configuration of a document and maintains a table of recognized parameters. | 
| DOMError | DOMErroris an interface that describes an error. | 
| DOMErrorHandler | 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). | 
| DOMException | 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). | 
| DOMImplementation | The  DOMImplementationinterface provides a number of methods for performing operations that are independent of any particular instance of the document object model. | 
| DOMImplementationList | The  DOMImplementationListinterface provides the abstraction of an ordered collection of DOM implementations, without defining or constraining how this collection is implemented. | 
| DOMImplementationSource | This interface permits a DOM implementer to supply one or more implementations, based upon requested features and versions, as specified in DOM Features. | 
| DOMLocator | DOMLocatoris an interface that describes a location (e.g. | 
| DOMStringList | The  DOMStringListinterface provides the abstraction of an ordered collection ofDOMStringvalues, without defining or constraining how this collection is implemented. | 
| Element | The  Elementinterface represents an element in an HTML or XML document. | 
| ElementTraversal | The  ElementTraversalinterface is a set of read-only attributes which allow an author to easily navigate between elements in a document. | 
| Entity | This interface represents a known entity, either parsed or unparsed, in an XML document. | 
| EntityReference | EntityReferencenodes may be used to represent an entity reference in the tree. | 
| NamedNodeMap | Objects implementing the  NamedNodeMapinterface are used to represent collections of nodes that can be accessed by name. | 
| NameList | The  NameListinterface 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. | 
| Node | The  Nodeinterface is the primary datatype for the entire Document Object Model. | 
| NodeList | The  NodeListinterface provides the abstraction of an ordered collection of nodes, without defining or constraining how this collection is implemented. | 
| Notation | This interface represents a notation declared in the DTD. | 
| ProcessingInstruction | The  ProcessingInstructioninterface represents a "processing instruction", used in XML as a way to keep processor-specific information in the text of the document. | 
| Text | The  Textinterface inherits fromCharacterDataand represents the textual content (termed character data in XML) of anElementorAttr. | 
| TypeInfo | The  TypeInfointerface represents a type referenced fromElementorAttrnodes, specified in the schemas associated with the document. | 
| UserDataHandler | When associating an object to a key on a node using  Node.setUserData()the application can provide a handler that gets called when the node the object is associated to is being cloned, imported, or renamed. | 
    © 1993, 2023, Oracle and/or its affiliates. All rights reserved.
Documentation extracted from Debian's OpenJDK Development Kit package.
Licensed under the GNU General Public License, version 2, with the Classpath Exception.
Various third party code in OpenJDK is licensed under different licenses (see Debian package).
Java and OpenJDK are trademarks or registered trademarks of Oracle and/or its affiliates.
    https://docs.oracle.com/en/java/javase/21/docs/api/java.xml/org/w3c/dom/package-summary.html