#34997 [Fbk->WFx]: nodeValue is set when should be null
| From: | rrichards@php.net | Date: | Wed, 26 Oct 2005 23:10:45 +0000 |
| Subject: | #34997 [Fbk->WFx]: nodeValue is set when should be null | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-87117@lists.php.net to get a copy of this message | ||
ID: 34997
Updated by: rrichards@php.net
Reported By: php dot net at punk dot co dot nz
-Status: Feedback
+Status: Wont fix
Bug Type: DOM XML related
Operating System: Windows XP
PHP Version: 5.0.5
New Comment:
This was done intentionally and as an extension to the DOM specs.
Provides quick access to Element content and is read-only for
DOMElement. This is the only node type that this exception was made
for.
Previous Comments:
------------------------------------------------------------------------
[2005-10-27 00:39:22] tony2001@php.net
Please try using this CVS snapshot:
http://snaps.php.net/php5-latest.tar.gz
For Windows:
http://snaps.php.net/win32/php5-win32-latest.zip
------------------------------------------------------------------------
[2005-10-27 00:37:58] php dot net at punk dot co dot nz
Description:
------------
The nodeValue attribute appears to be set to the concatenation of the
contents of all child text nodes.
As far as I understand according to the specification (p36,
DOM2-Core.pdf, w3.org) the nodeValue should be set to NULL for Element
node types (and many other node types).
This may be a problem for other node types as well.
Reproduce code:
---------------
http://www.punk.co.nz/php.net/nodeValue-test.zip
Includes a sample xml file and output.txt.
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=34997&edit=1