- From: Stephen R. Savitzky <steve@crc.ricoh.com>
- Date: 08 Sep 1998 17:05:25 -0700
- To: keshlam@us.ibm.com
- Cc: www-dom@w3.org
keshlam@us.ibm.com writes: > So Document.createCopy() would become the "xeno-copy" routine we've > discussed in the past, which copies a DOM node "by content" rather than > cloning the actual object? Sounds like a good answer to me; [...] Right. > Normal cloneNode() would continue to be defined on Node itself. > We'd still have to decide whether Document.cloneNode() should be > reinterpreted as "Create a new document and createCopy() of the old > document's contents" or simply be disabled. I would think that Document.cloneNode should be reinterpreted as you suggest -- having createCopy makes it very easy to describe the desired functionality. -- Stephen R. Savitzky Chief Software Scientist, Ricoh Silicon Valley, Inc., <steve@rsv.ricoh.com> California Research Center voice: 650.496.5710 fax: 650.854.8740 URL: http://rsv.ricoh.com/~steve/ home: <steve@starport.com> URL: http://www.starport.com/people/steve/
Received on Tuesday, 8 September 1998 19:59:04 UTC