Yep! It is fixed.
Thank you Fabian.
Regards
Fabian Jakobs schrieb:
> Hello Dietrich,
>
> I have modified the order, the msxml implementations are searched.
> msxml3 is now the preferred implementation. This should fix this issue.
>
> Best Fabian
>
>
>
> -
Hello Dietrich,
I have modified the order, the msxml implementations are searched.
msxml3 is now the preferred implementation. This should fix this issue.
Best Fabian
-
Take Surveys. Earn Cash. Influence the Future of IT
Dietrich Streifert schrieb:
> I'v tried your test. The problem is there. Here is the content of the
> debug area:
>
> qx.core.Init[3]
> 000406: qooxdoo 0.7-pre (r5009)
> 000422: loaded 278 classes
> 000422: client: mshtml-7.0/win/de
> qx.component.init.InterfaceInitComponent[29]
> 000422: initiali
I'v tried your test. The problem is there. Here is the content of the
debug area:
qx.core.Init[3]
000406: qooxdoo 0.7-pre (r5009)
000422: loaded 278 classes
000422: client: mshtml-7.0/win/de
qx.component.init.InterfaceInitComponent[29]
000422: initialize runtime: 0ms
000484: main runtime: 62ms
0
Hello Dietrich,
I'm currently testing my application against IE7. I'm using
XMLHttpRequest (via RemoteRequest) and doing sometimes manipulations of
the received XML document.
In some scenarios I need to create a xml document and copy nodes from
one document to the other, in this case from a x
As a first workarround I've overridden the class method
qx.io.remote.XmlHttpTransport.isSupported so the test for native xmlhttp
fails if the client is mshtml:
if (window.XMLHttpRequest && !qx.sys.Client.getInstance().isMshtml())
Dietrich Streifert schrieb:
> Hello List,
>
> I'm currently t
Hello List,
I'm currently testing my application against IE7. I'm using
XMLHttpRequest (via RemoteRequest) and doing sometimes manipulations of
the received XML document.
In some scenarios I need to create a xml document and copy nodes from
one document to the other, in this case from a xmlhtt
