[
https://jira.jboss.org/browse/RF-9485?page=com.atlassian.jira.plugin.syst...
]
Andrew May commented on RF-9485:
--------------------------------
We have apps that won't get upgraded to RichFaces 4 any time soon, but will have IE9
users as soon as it's released.
Presumably if Sarissa gets fixed we could drop the new sarissa.js into the 3.3 release and
build it ourselves?
The alternative seems to be to advise them to use compatibility mode if we detect
they're using IE9.
IE9 Beta - AJAX broken
----------------------
Key: RF-9485
URL:
https://jira.jboss.org/browse/RF-9485
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: browser compatibility
Affects Versions: 3.3.2.SR1, 3.3.3.Final
Environment: Windows Vista SP2 (Virtual PC VM), IE9 Beta
Reporter: Andrew May
Assignee: Nick Belaevski
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 contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira