Probably too late to be considered for 1.3, but I thought I'd ask anyway...
I'm seeing an upcoming problem in that the Encryption/Decryption calls assume that I want to replace the nodes being fed in with the result (in either direction). In my particular library, this will cause some problems because of the objects I've got wrapped around the DOM and I'd prefer to manage the node replacement myself when I'm ready to do it. It occurs to me that I could maybe work around it if the old nodes aren't explicitly wrecked or disposed of by the API calls, but I haven't tried it yet, and it would be simpler to be able to signal that somehow. Is that possible? -- Scott
