Re: Possible error with DOMNode::replaceChild() in 5.0.4

Please bug this. James Crumpton wrote:

Now, that may in fact be the proper way to handle things... however, it was very handy to be able to replace a single node with multiple top level nodes (what DocumentFragments are good for in the first place), and then being able to further process all those top level nodes by referencing the DocumentFragment, rather than writing a bunch of code to try and figure out which nodes were newly added.

Behavior was wrong, inconsistant with append behavior and breaks xsl, xpath and a few other things. Rob