Re: Accessing the original XML DOM after browser-applied XSL transformation?
Axel Hecht <[email protected]>
| Newsgroups | gmane.comp.mozilla.devel.xml |
|---|---|
| Organization | Another Netscape Collabra Server User |
| Message-ID | <[email protected]> |
Martin Honnen wrote: > > > Christian Biesinger wrote: > >> Martin Honnen wrote: >> >>> But as far as I understand these are readonly so what the original >>> poster expects, e.g. changing the source XML with DOM manipulation >>> and having the result document automatically updated, is not possible. >> >> >> "readonly" here only means that you can't do "document.XMLDocument = >> foo;", doesn't it? It doesn't necessarily mean that you can't change >> the DOM. > > When I wrote that I had some recollection that I had long ago attempted > to change the DOM and it would not work. But I have tried now and you > can change the DOM of document.XMLDocument. But an automatic update of > the result document rendered in the browser does not happen, one needs > to run the transformation using the MSXML methods (e.g. tranformNode) > and then use IE DOM stuff (e.g. innerHTML, insertAdjacentHTML) to have > the string result of transformNode parsed and inserted into IE's HTML > DOM document. > Which is actually pretty cool, as you don't end up transforming over and over for multiple changes to the DOM on the one side, on the other side, you don't mess with content in inputs, or other js modifications to the DOM that once got js generated. Axel