W3C home > Mailing lists > Public > www-dom@w3.org > October to December 1999

Node.replaceChild with newChild being a DocumentFragment

From: Takuki Kamiya <kamiya@rp.open.cs.fujitsu.co.jp>
Date: Fri, 26 Nov 1999 01:01:43 +0900
Message-ID: <026201bf375e$6fa1ee40$8af5a8c0@246.ne.jp>
To: <www-dom@w3.org>
DOM L2 WD (as well as L1 spec indeed) appears to fail to be clear as to
what behavior to be expected when Node.replaceChild is invoked with its
newChild being a DocumentFragment. Other methods such as insertBefore
and appendChild are explicitly stated as being aware of DocumentFragment
on the other hand.

I suggest that DOM L2 be specific on this point.
I know of DOM implementations which behaves differently upon the operation
described above: one raises HIERARCHY_REQUEST_ERR exception, the other
succeeds so that the net result is the same as if removeChild was
called following insertBefore. This is not apparently a desirable
situation for DOM interoperability thus needs to be explicitly described
in the spec one way or the other.

= Takuki Kamiya  Phone: (045)476-4586 Fax: (045)476-4749   =
= FUJITSU LIMITED (COINS:7128-4217 NIFTY:HHA01731)         =
Received on Thursday, 25 November 1999 10:51:19 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 June 2012 06:13:47 GMT