Reputation: 57274
PHP DOMnode objects contain a textContent and nodeValue attributes which both seem to be the innerHTML of the node.
nodeValue: The value of this node, depending on its type
textContent: This attribute returns the text content of this node and its descendants.
What is the difference between these two properties? When is it proper to use one instead of the other?
Upvotes: 55
Views: 45204
Reputation: 4113
Both textContent
and nodeValue
return unescaped text; i.e. <
becomes <
.
textContent
concatenates together all of the content of all children. This is an important distinction; for example, in Chrome the maximum length of nodeValue
is 65536 characters (not bytes); if you have already set the content of a node to something longer than that you will need to iterate child nodes if you want to use nodeValue
whereas textContent
will perform the concatenation for you.
As discussed, there are also several DOM classes that do not support nodeValue
but do support textContent
.
nodeValue
is faster for obvious reasons; however don't use it unless you know exactly what the node structure really is.
Upvotes: 10
Reputation: 1522
If you want to assigning a value to the textContent
property note that it doesn't work for PHP < 5.6.1. Consider using nodeValue
instead, for backward compatibility.
Upvotes: 0
Reputation: 173652
I finally wanted to know the difference as well, so I dug into the source and found the answer; in most cases there will be no discernible difference, but there are a bunch of edge cases you should be aware of.
Both ->nodeValue
and ->textContent
are identical for the following classes (node types):
The ->nodeValue
property yields NULL
for the following classes (node types):
The ->textContent
property is non-existent for the following classes:
DOMNameSpaceNode
(not documented, but can be found with //namespace:*
selector)The ->nodeValue
property is non-existent for the following classes:
See also: dom_node_node_value_read()
and dom_node_text_content_read()
Upvotes: 51
Reputation: 55002
They're the same thing. (mikespook's NULL is from a non-DOMNode)
Upvotes: -4
Reputation: 796
Hope this will make sense:
$doc = DOMDocument::loadXML('<body><!-- test --><node attr="test1">old content<h1>test</h1></node></body>');
var_dump($doc->textContent);
var_dump($doc->nodeValue);
var_dump($doc->firstChild->textContent);
var_dump($doc->firstChild->nodeValue);
Output:
string(15) "old contenttest"
NULL
string(15) "old contenttest"
string(15) "old contenttest"
Because: nodeValue - The value of this node, depending on its type
Upvotes: 20