]
Nicolas Daniels edited comment on RF-9485 at 4/3/12 7:06 AM:
-------------------------------------------------------------
Here is my non empty Ajax.js. I'm currently using it without problem.
Additional change I've performed to fix IE9 issue:
line 464:
if(!window.DOMParser || Sarissa._SARISSA_IS_IE9)
was (Author: multanis):
Non empty Ajax.js
IE9 Beta - AJAX broken
----------------------
Key: RF-9485
URL:
https://issues.jboss.org/browse/RF-9485
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: compatibility
Affects Versions: 3.3.2.SR1, 3.3.3.Final
Environment: Windows Vista SP2 (Virtual PC VM), IE9 Beta
Reporter: Andrew May
Labels: ie9
Fix For: 3.Future
Attachments: AJAX.js, AJAX.js, AJAX.js, IE9.txt, JSFAJAX.txt, sarissa.js
In the Rich Faces Demo (3.3.3 Final) there are a couple of errors shown in the JavaScript
Console in IE9, and the Ajax demos do not work.
On loading a section:
SCRIPT5007: 'undefined' is null or not an object - framework.pack.js.jsf, line
1870 character 65
On trying one of the AJAX demos (e.g. the CommandButton demo):
SCRIPT16386: No such interface supported - framework.pack.js.jsf, line 2373 character 3
In our applications (3.2.SR1), we see an error for every Ajax request:
SCRIPT16386: No such interface supported - 3_3_2.SR1org.ajax4jsf.javascript.AjaxScript,
line 120 character 1
For both the SCRIPT16386 errors, the JavaScript is assigning A.outerHTML = new
XMLSerializer().serializeToString(C)
I believe that this is the first version of IE9 to include XMLSerializer.
I don't know enough about XMLSerializer to know whether this is an IE9 issue or a
RichFaces issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: