[richfaces-issues] [JBoss JIRA] (RF-11529) a4j:support in rich:datatable JS crash in Chrome with limitToList="true"

[Markus Staab (JIRA)]

    [ https://issues.jboss.org/browse/RF-11529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12663768#comment-12663768 ] 

Markus Staab commented on RF-11529:
-----------------------------------

I tracked it down a little bit more...

in case a <script type="..."></script> will be rendered inside the table it will stop working on Webkit (Chrome or Safari)
                
> a4j:support in rich:datatable JS crash in Chrome with limitToList="true"
> ------------------------------------------------------------------------
>
>                 Key: RF-11529
>                 URL: https://issues.jboss.org/browse/RF-11529
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: third-party
>    Affects Versions: 3.3.3.Final
>         Environment: Tomcat 7, RichFaces 3.3.3.Final
>            Reporter: Stef Klaassen
>            Priority: Minor
>             Fix For: 3.Future
>
>
> I've got a Datatable in which I have a column that contains a tomahawk selectOneRadio. In this selectOneRadio is a a4j:support that has an onclick event to update some components. On this support-tag I had the limitToList-attribute set to true. This works fine in FF and IE, but today I tested it in Chrome and I saw that the Javascript wasn't executed anymore. When I click a radiobutton first, which makes another button in the next column dissapear, all goes well. But when I click another radiobutton that should make the next column button reappear again, it fails. 
> I get the following error in chrome:
> {quote}
> Uncaught Error: Uncaught Error: NOT_SUPPORTED_ERR: DOM Exception 9 3_3_3.Finalorg.ajax4jsf.javascript.AjaxScript.html:121 
> {quote}
> which points at this line: 
> {code}
> var importednode=window.document.importNode(newnode,true);
> {code}

--
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