[ https://issues.jboss.org/browse/RF-11266?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-11266: ------------------------------------ Javascript error thrown when the first item is expanded: {noformat} SCRIPT5007: Unable to get value of the property '__fireToggleEvent': object is null or undefined tree.js.jsf?ln=org.richfaces, line 304 character 9 {noformat} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-11266?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-11266: ------------------------------------ Replacing the data store/retrieval mechanism with the jQuery "data" method had no effect. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-11266?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-11266: ------------------------------------ I isolated the point at which we are unable to retrieve the javascript object from the DOM node. It occurs when the _component_ is detached from the DOM, and subsequently re-attached. {code:title=richfaces.js, line 89} //dom cleaner richfaces.cleanComponent = function (source) { var component = richfaces.$(source); if (component) { //TODO fire destroy event component.destroy(); component.detach(source); } var attachedComponents = richfaces.findNonVisualComponents(source); if (attachedComponents) { for (var i in attachedComponents) { if (attachedComponents[i]) { attachedComponents[i].destroy(); } } } }; {code} jQuery data is supposed to persist detaching, do further investigation is required as to why this is happening. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-11266?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-11266: ------------------------------------ The reason the above exception is thrown, is because the _deleteNode_ method in jsf.js has special handling in it for IE {code:title=jsf.js, line 551} /** * Deletes node * @param node * @ignore */ var deleteNode = function deleteNode(node) { if (!node) { return; } if (!isIE()) { // nothing special required if (!node.parentNode) { // if there's no parent, there's nothing to do return; } node.parentNode.removeChild(node); return; } // The rest of this code is specialcasing for IE if (node.nodeName.toLowerCase() === "body") { // special case for removing body under IE. deleteChildren(node); try { node.outerHTML = ''; } catch (ex) { // fails under some circumstances, but not in RI // supplied responses. If we've gotten here, it's // fairly safe to leave a lingering body tag rather than // fail outright } return; } var temp = node.ownerDocument.createElement('div'); var parent = node.parentNode; temp.appendChild(parent.removeChild(node)); // Now clean up the temporary element try { temp.outerHTML = ''; //prevent leak in IE } catch (ex) { // at least we tried. Fails in some circumstances, // but not in RI supplied responses. Better to leave a lingering // temporary div than to fail outright. } }; {code} The exception is thrown when the IE specific code is run. If the execution path is altered to not run the IE specific code, then the component behaves as expected. It seems as though this is a known JSF issue: http://java.net/jira/browse/JAVASERVERFACES-2063 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-11266?page=com.atlassian.jira.plugin.s... ] Juraj Huska updated RF-11266: ----------------------------- Labels: ie9_normal_jq151 (was: ie9) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira