[ https://issues.jboss.org/browse/RF-11838?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-11838: ------------------------------------ This is an upstream problem with jQuery ([issue 10531 | http://bugs.jquery.com/ticket/10531]), and will be resolved when we upgrade to jQuery 1.7. Created RF-11847 to track upgrading jQuery. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-11838?page=com.atlassian.jira.plugin.s... ] Brian Leathem resolved RF-11838. -------------------------------- Resolution: Duplicate Issue -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-11838?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak reopened RF-11838: -------------------------------- I see the warning in Chrome's console after jQuery upgrade (jQuery.fn.jquery returns 1.7.1). {quote} RichFaces 4.1.1-SNAPSHOT Metamer 4.1.1-SNAPSHOT Mojarra 2.1.5 JBoss AS 7.1.0.CR1 OpenJDK Runtime Environment 1.6.0_22-b22 @ Linux Chrome 16.0.912.75 @ Linux i686 {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-11838?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-11838: ------------------------------------ In richfaces-queue.js, we copy the event (otherwise IE fails) on [Line 129|https://github.com/richfaces/core/blob/develop/impl/src/main/resource...]: {code:title=richfaces-queue.js|Line 129} this.event = $.extend({}, event); {code} Since layerX and layerY are still properties of the Webkit event (they have not *yet* been removed), we are copying them in our event copy. The access to the event properties triggers the error. On solution is to remove the properties from the event prior to copying the event, as investigated quite thoroughly by the jsperf team: http://jsperf.com/removing-event-props/2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-11838?page=com.atlassian.jira.plugin.s... ] Pjotr Andreev commented on RF-11838: ------------------------------------ ??4.2.0-SNAPSHOT Showcase->Ajax Action->a4j:ajax->Dynamic Selects??: I think there must be one more check for event.layerX in richfaces-queue.js, line 129, otherwise the ajax req fails on IE8 (or on IE9/<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE8"/>) with "SCRIPT438: Object doesn't support this property or method richfaces-queue.js.jsf, line 130 character 17": {code:title=richfaces-queue.js|borderStyle=dashed} // Remove the layerX and layerY events (generated in WebKit browsers) if (event && event.layerX) { delete event.layerX; delete event.layerY; } {code} I`ve tested it with FF13, IE8/Win7, IE9(EmulateIE8) and Chrome- no errors -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira