Last post Jul 28, 2015 08:20 AM by Rion Williams
Jul 24, 2015 02:38 PM|crazzeto|LINK
So I'm playing around with testing some legacy ajax code on Edge browser and have noted that it is not functional. It is failing to properly load the XMLDOM object. The essential logic is below. Basically what is happening is that the code gets routed to
"else" attempting to create a document.implementation.createDocument. This does not seem to be a XMLDOM type object, though an object is indeed return (loadXML not supported for instance).
Our legacy XML uses XMLDom to create XML documents which are posted to a service handler which in turn returns a response. Is there documentation anywhere on how this would be done with Edge?
+ rootTagName + "></"
+ rootTagName + ">");
domObject = document.implementation.createDocument("",
Jul 24, 2015 04:27 PM|Rion Williams|LINK
It looks like you are attempting to target an ActiveX object, which if memory serves,
is a no-no within the upcoming Edge browser. Since Edge is still under development, I'm not sure how much documentation is going to be available and how much of that is going to be published publicly at this point.
You may want to consider contacting the Edge team on Twitter (@MSEdgeDev) and they may be able to answer your question in more detail or get in touch with you.
Jul 28, 2015 08:05 AM|crazzeto|LINK
Too be more accurate I'm trying to load the proper version of XMLDOM via feature detection. So taking another look at the code logically it should be -
if active x feature exists then
load XMLDOM via active x
if this feature does not exist then
load xml dom by document.implementation.createDocumet(.....)
I feel like there needs to be another condition where end occurs to get XMLDOM, that or Microsoft is somehow changing the functionality of XMLDOM. I realize Edge is still "under development" but isn't that really only true (as such) until tomorrow? Given
the fact that everyone who reserved a copy will be waking up to shiny new Windows 10 installs shortly, should there not be some documentation somewhere at this point?
Jul 28, 2015 08:20 AM|Rion Williams|LINK
As I mentioned earlier, I'm not entirely sure that Edge is going to support Active X based on the earlier article that I provided. Have you tried reaching out to the Edge team? They would be the most likely to know the details regarding things like usage
of the XMLDOM, etc.
Given the fact that everyone who reserved a copy will be waking up to shiny new Windows 10 installs shortly, should there not be some documentation somewhere at this point?
Sadly, this is rarely the case with documentation. I'm sure it will eventually emerge, but I wouldn't expect a very verbose or extensive set of it by release.