[
https://issues.apache.org/jira/browse/WICKET-3887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13064728#comment-13064728
]
Walter B. Rasmann edited comment on WICKET-3887 at 7/13/11 5:55 PM:
--------------------------------------------------------------------
Thank you for your fast response and for dealing with this issue!
Unfortunately there is still a problem.
I tested the latest Wicket-1.4 SNAPSHOT with IE9:
https://repository.apache.org/content/groups/snapshots/org/apache/wicket/wicket/1.4-SNAPSHOT/wicket-1.4-20110713.000152-600.jar
Here is an excerpt from the WICKET-AJAX-DEBUG log:
INFO: Using XMLHttpRequest transport
[…]
INFO: Received ajax response (1114 characters)
[…]
ERROR: Wicket.Ajax.Call.failure: Error while parsing response:
Automation server can't create object
The following three sections of code have been executed in that order:
wicket-ajax.js(724):
>var transport = null;
>
>if (window.XMLHttpRequest) {
>
> transport = new XMLHttpRequest();
>
> Wicket.Log.info("Using XMLHttpRequest transport");
>
>} else if (window.ActiveXObject) {
>
> transport = new ActiveXObject("Microsoft.XMLHTTP");
>
> Wicket.Log.info("Using ActiveX transport");
>
>}
wicket-ajax.js(1038):
>var xmldoc;
>
>if (typeof(window.XMLHttpRequest) != "undefined" && typeof(DOMParser) !=
>"undefined") {
> var parser = new DOMParser();
>
> xmldoc = parser.parseFromString(responseAsText, "text/xml");
>
>} else if (window.ActiveXObject) {
>
> xmldoc = t.responseXML;
>
>}
wicket-ajax.js(1516):
>var xmldoc;
>
>if (window.ActiveXObject) {
>
> xmldoc = new ActiveXObject("Microsoft.XMLDOM");
>
> if (!xmldoc.loadXML(text)) {
>
> Wicket.Log.error("Error parsing response: "+text);
>
> }
>
>} else {
>
> var parser = new DOMParser();
>
> xmldoc = parser.parseFromString(text, "text/xml");
>
>}
The last one caused an exception.
was (Author: wicket.x.ttp):
Thank you for your fast response and for dealing with this issue!
Unfortunately there is still a problem.
I tested the latest Wicket-1.4 SNAPSHOT with IE9:
https://repository.apache.org/content/groups/snapshots/org/apache/wicket/wicket/1.4-SNAPSHOT/wicket-1.4-20110713.000152-600.jar
Here is an excerpt from the WICKET-AJAX-DEBUG log:
INFO: Using XMLHttpRequest transport
[…]
INFO: Received ajax response (1114 characters)
[…]
ERROR: Wicket.Ajax.Call.failure: Error while passing response:
Automation server can't create object
The following three sections of code have been executed in that order:
wicket-ajax.js(724):
>var transport = null;
>
>if (window.XMLHttpRequest) {
>
> transport = new XMLHttpRequest();
>
> Wicket.Log.info("Using XMLHttpRequest transport");
>
>} else if (window.ActiveXObject) {
>
> transport = new ActiveXObject("Microsoft.XMLHTTP");
>
> Wicket.Log.info("Using ActiveX transport");
>
>}
wicket-ajax.js(1038):
>var xmldoc;
>
>if (typeof(window.XMLHttpRequest) != "undefined" && typeof(DOMParser) !=
>"undefined") {
> var parser = new DOMParser();
>
> xmldoc = parser.parseFromString(responseAsText, "text/xml");
>
>} else if (window.ActiveXObject) {
>
> xmldoc = t.responseXML;
>
>}
wicket-ajax.js(1516):
>var xmldoc;
>
>if (window.ActiveXObject) {
>
> xmldoc = new ActiveXObject("Microsoft.XMLDOM");
>
> if (!xmldoc.loadXML(text)) {
>
> Wicket.Log.error("Error parsing response: "+text);
>
> }
>
>} else {
>
> var parser = new DOMParser();
>
> xmldoc = parser.parseFromString(text, "text/xml");
>
>}
The last one caused an exception.
> Problems concerning IE9 with "ActiveX Filtering" enabled
> --------------------------------------------------------
>
> Key: WICKET-3887
> URL: https://issues.apache.org/jira/browse/WICKET-3887
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core
> Affects Versions: 1.4.17
> Environment: Windows 7, Internet Explorer 9, "ActiveX Filtering"
> enabled (for example as a domain policy in a company)
> Reporter: Walter B. Rasmann
> Assignee: Martin Grigorov
> Priority: Minor
> Fix For: 1.4.18
>
> Original Estimate: 8h
> Remaining Estimate: 8h
>
> Internet Explorer 9 contains a new feature to block all ActiveX content by
> default:
> http://ie.microsoft.com/testdrive/Browser/ActiveXFiltering/About.html
> If the feature is enabled, all ActiveX controls are blocked silently. With
> Wicket this currently results in a lot of JavaScript content (but not all of
> it) being blocked as well. The user can allow an exception by clicking on a
> small icon in the address bar, however, he usually will be only able to do
> so, if he knows exactly what causes the problem.
> A user who enabled the feature himself might still see what is wrong, but the
> feature can be also enabled in a domain policy, which might make solving the
> problem much more difficult and have adverse effects on customers.
> The reason that some JavaScript content is blocked along with blocking
> ActiveX elements is the usage of window.ActiveXObject:
> wicket-ajax.js:
> >if (window.ActiveXObject) {
> >
> > transport = new ActiveXObject("Microsoft.XMLHTTP");
> >
> > Wicket.Log.info("Using ActiveX transport");
> >
> >} else if (window.XMLHttpRequest) {
> >
> > transport = new XMLHttpRequest();
> >
> > Wicket.Log.info("Using XMLHttpRequest transport");
> >
> >}
> According to
>
> http://blogs.msdn.com/b/ie/archive/2011/05/02/activex-filtering-for-developers.aspx
>
> the usage of this pattern is not advisable and the order should be changed to:
> >// Best Practice: Use Native XHR, if available
> >if (window.XMLHttpRequest) {
> > // If IE7+, Gecko, WebKit: Use native object
> > var xmlHttp = new XMLHttpRequest();
> >}
> >else if (window.ActiveXObject) {
> > // ...if not, try the ActiveX control
> > var xmlHttp = new ActiveXObject("Microsoft.XMLHTTP");
> >}
> The problem is reported to be fixed in JQuery 1.5.1, for instance.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
