[
https://jira.jboss.org/jira/browse/JBSEAM-3459?page=com.atlassian.jira.pl...
]
Anthony Kitchin commented on JBSEAM-3459:
-----------------------------------------
In my testing the only instance of onreadystatechange that I modified was the one within
the Seam.Remoting.requestCallback. I think the better thing to do would be to chnage the
Seam.Remoting.sendAjaxRequest back to the way it was before r9167. but leave the
Seam.Remoting.requestCallback the way it currently is.
IE6 (very specific version) Crash on Seam Remoting Callback
-----------------------------------------------------------
Key: JBSEAM-3459
URL:
https://jira.jboss.org/jira/browse/JBSEAM-3459
Project: Seam
Issue Type: Bug
Components: Remoting
Affects Versions: 2.0.1.GA
Environment: Microsoft Windows XP - Professional
IE 6.0.2900.2180.xpsp_sp2_gdr.070227-2254
Intel (R) Core(TM) 2 Duo CPU (1.80Ghz)
1.99Gb of RAM
Reporter: Anthony Kitchin
Assignee: Shane Bryzak
Fix For: 2.1.0.GA
I tracked the issue down to one line of javascript code in remote.js
req.onreadystatechange = function() {};
The following thread discusses the problem is with an old version of the JScript.dll
5.6.0.8820 which is the same version I've got on a laptop here.
http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/69...
One solution is to upgrade JScript.dll to 5.6.0.8831
http://www.microsoft.com/technet/security/bulletin/ms06-023.mspx
Or we can do what they did in GWT which is to move the req.onreadystatechange out of the
scope of the current function
window.setTimeout(function() {
req.onreadystatechange = function() {};
}, 0 );
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira