All Implemented Interfaces:
CharacterData
All Known Implementing Classes:
CDATASection
Text
interface inherits from CharacterData
and represents the textual content (termed character data in XML) of an Element
or Attr
. If there is no
markup inside an element's content, the text is contained in a single
object implementing the Text
interface that is the only
child of the element. If there is markup, it is parsed into the
information items (elements, comments, etc.) and Text
nodes
that form the list of children of the element.
When a document is first made available via the DOM, there is only one
Text
node for each block of text. Users may create adjacent
Text
nodes 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. The
Node.normalize()
method merges any such adjacent
Text
objects into a single node for each block of text.
No lexical check is done on the content of a Text
node
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.
See also the Document Object Model (DOM) Level 3 Core Specification.
Method from org.w3c.dom.Text Summary: |
---|
getWholeText, isElementContentWhitespace, replaceWholeText, splitText |
Method from org.w3c.dom.Text Detail: |
---|
Text nodes logically-adjacent text
nodes to this node, concatenated in document order.
For instance, in the example below wholeText on the
Text node that contains "bar" returns "barfoo", while on
the Text node that contains "foo" it returns "barfoo". |
Document.normalizeDocument() . |
This method returns the node which received the replacement text. The returned node is: For instance, in the above example calling replaceWholeText on the Text node that
contains "bar" with "yo" in argument results in the following:
Where the nodes to be removed are read-only descendants of an EntityReference , the EntityReference must
be removed instead of the read-only nodes. If any
EntityReference to be removed has descendants that are
not EntityReference , Text , or
CDATASection nodes, the replaceWholeText
method must fail before performing any modification of the document,
raising a DOMException with the code
NO_MODIFICATION_ALLOWED_ERR .
For instance, in the example below calling replaceWholeText on the Text node that
contains "bar" fails, because the EntityReference node
"ent" contains an Element node which cannot be removed. |
offset ,
keeping both in the tree as siblings. After being split, this node
will contain all the content up to the offset point. A
new node of the same type, which contains all the content at and
after the offset point, is returned. If the original
node had a parent node, the new node is inserted as the next sibling
of the original node. When the offset is equal to the
length of this node, the new node has no data. |