Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: get DOM Tree from transformation

From: "VK" <schools_ring@-----.--->
To: NULL
Date: 1/3/2007 8:25:00 AM


Martin Honnen wrote:
> That does not work if document.body is the body of an HTML DOM document.
> The XML DOM implementation (of MSXML) and the HTML DOM implementation
> (of IE/MSHTML) are separate implementations, you are not able to move
> nodes from an XML DOM document to a HTML DOM document. If your intention
> is to transform XML to HTML with XSLT then with IE you are bound to use
> transformNode to get a string result and insert that string into the
> HTML document with innerHTML or insertAdjacentHTML.

While waiting for responces I looked on Sarissa doing on this matter.
<http://sarissa.sourceforge.net/doc/overview-summary-sarissa.js.html>
You are seem right: with IE you are either happy with
insertAdjacentHTML or you are using rather ugly hacks like the one on
Sarissa - to bring appendChild back to life.

Taking into account that to get rid off insertAdjacentHTML was the
original purpose of our library remodeling - it puts a rather hard
choice :-)   :-(

Thanks everyone.



transparent
Print
Mail
Digg
delicious
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent