Replies

I have been using Trusteer for some time. Lately logging on to any HTTPS site became very slow (both FF and IE9) would just freeze up for 30 seconds. In some cases it froze completely and after that the only remedy was to reboot the machine 🙁

An Internet search suggested that the problem could be Trusteer and that it should be uninstalled, the latest version downloaded and installed again. That solved the problems completely.

I never had Google Chrome installed; this is a fairly new computer.
So I have just downloaded and installed Google Chrome and it fixed the problem!
Closed Chrome and made IE the default browser. Still fixed.
Well, well; you need Google Chrome to fix an Office 2010 problem. I would like to ge a technical explanation for this. Guess I should not uninstall Chrome now…

Thanks for the link!

Yes, I have done all of that. My specific problem is with links to local files (e.g. another spreadsheet or Word file) although web URLs give the same problem.

Unfortunately, yes. That is what I refer to as the “HTML hyperlinks and IE not being the default browser” solutions in my message.

The subsequent request is actually a completely new request. Here is the code:

Code:

var xhttp=0;

function XhRequest(name)
{
 if (xhttp) {  // this code not required for IE/FF; unsuccessful attempt to get Chrome to work
  xhttp.abort();
  delete xhttp;
  xhttp=0;
 }
 if (window.XMLHttpRequest){
  xhttp=new XMLHttpRequest()
 }
 else{
  xhttp=new ActiveXObject("Microsoft.XMLHTTP")
 }
 xhttp.open("POST",name,true);
 xhttp.onreadystatechange=checkXHR;
 xhttp.send(session);
}

I found a solution, but I’m not too happy with it; if not a bug, it is a serious shortcoming of Chrome.

The subsequent request is initiated by setting a timeout in the onreadystatechange handler which will issue the next request after the timeout:

Code:

function checkXHR()
{
 if (xhttp.readyState!=4)
   return;
 // read XML and build screen
 setTimeout("XhRequest('data3270.xml')",400);
}

With IE and FF I can use a timeout of 50 ms, with Chrome it needs to be 400 ms.

Does your code set any conditions on issuing the subsequent request? Just wondering whether you’re checking for some value that differs after abort() in different browsers.

The subsequent request is actually a completely new request. Here is the code:

Code:

var xhttp=0;

function XhRequest(name)
{
 if (xhttp) {  // this code not required for IE/FF; unsuccessful attempt to get Chrome to work
  xhttp.abort();
  delete xhttp;
  xhttp=0;
 }
 if (window.XMLHttpRequest){
  xhttp=new XMLHttpRequest()
 }
 else{
  xhttp=new ActiveXObject("Microsoft.XMLHTTP")
 }
 xhttp.open("POST",name,true);
 xhttp.onreadystatechange=checkXHR;
 xhttp.send(session);
}