IE10/IE11 using XMLHTTPRequest is adding Cr/Lf in arbitrary places to XML data.
If you have a web page that provides simple XML data like:
<data><item>Hello World</item><item>Life is grand</item><item>Smiles keep you healthy</item></data>
If you consume this data using the XMLHTTPRequest and then analyze the responseXML, you can find \r\n or 
 when there is no cr/lf in the data.
This is not the behavior of the activeX XMLHTTP object and this behavior is not standard (Chrome, Mozilla, Safari, etc). Why are there random cr/lf inserted in the XML Data? It creates huge issues with our system and XSLT rendering.
I can provide code and data if needed. Please, can someone at MS explain why they started putting Cr/Lf in the responseXML? Is there a property that can be set to remove those.
There is a thread on stackoverflow submitted by one of our programmers about this issue, and IE11 seems to have taken the issue further by returning false to window.ActiveX making it more difficult to override the use of the new XMLHTTPRequest.
And my post which is the same issue but manifests itself in a different way (putting 
 where a space is in quotes) after XSLT transformation.
http://stackoverflow.com/questions/20363235/ie-11-xslt-xml-bug