Bug #68512 [Opn]: DOMDocument specific properties in child class not used.
Edit report at https://bugs.php.net/bug.php?id=68512&edit=1
ID: 68512
Updated by: levim@php.net
Reported by: arjen at react dot com
Summary: DOMDocument specific properties in child class not
used.
Status: Open
Type: Bug
Package: DOM XML related
Operating System: Linux
PHP Version: 5.6.3
Block user comment: N
Private report: N
New Comment:
Further examination of the manual shows that some of DomDocument's properties are explicitly
read-only while others are not. I am not sure what the exact reason for this is. Assuming that none
of the properties are actually writable, I propose changing the docs to list that they are all
read-only properties.
Previous Comments:
------------------------------------------------------------------------
[2014-12-28 19:08:14] levim@php.net
I'm inclined to say the var_dump output is what is incorrect. I believe DOMDocument's
properties are read-only by design and should remain that way.
------------------------------------------------------------------------
[2014-11-27 08:20:52] arjen at react dot com
Description:
------------
When extending DOMDocument, it's class properties cannot be overwritten/changed.
DOMDocument's initial value are kept.
var_dump() however contains the actual new value, so behaviour is buggy at least.
See http://3v4l.org/6H88X
Test script:
---------------
<?php
class A extends DOMDocument
{
public $formatOutput = true;
}
$a = new A;
var_dump($a->formatOutput); // false
var_dump($a); // Has formatOutput => true
Expected result:
----------------
bool(true)
object(A)#1 (34) {
["formatOutput"]=>
bool(true)
<<cut>>
}
Actual result:
--------------
bool(false)
object(A)#1 (34) {
["formatOutput"]=>
bool(true)
<<cut>>
}
------------------------------------------------------------------------
--
Edit this bug report at https://bugs.php.net/bug.php?id=68512&edit=1
Thread (3 messages)