[ https://issues.apache.org/jira/browse/MYFACES-2585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12841741#action_12841741 ]
Ganesh Jung commented on MYFACES-2585: -------------------------------------- Werner, you are right. Removing enclosing CDATA like Mojarra does is just a hack that fails in many cornercases. How do you want to mark the encoded sections? Wouldn't you use again some special characters that may be part of a regular xhtml page? Another problem of the base64 approach is the loss of readability of the xhr response. I like using the console output in firebug to see what my ajax responses actually are. With base64 I'd only see some salad instead. Any ideas how to solve these? > ajax doesn't work if target contains script with CDATA > ------------------------------------------------------ > > Key: MYFACES-2585 > URL: https://issues.apache.org/jira/browse/MYFACES-2585 > Project: MyFaces Core > Issue Type: Bug > Components: JSR-314 > Affects Versions: 2.0.0-beta-2 > Environment: Javascript, API, IMPL... > Reporter: Ganesh Jung > Priority: Critical > > This doesn't work: > <h:inputText value="#{numberBean.myNumber}"> > <f:ajax render="test" /> > </h:inputText> > <h:panelGroup id="test"> > <script type="text/javascript"> > //<![CDATA[ > alert("running"); > //]]> > </script> > <h:inputText value="#{numberBean.myNumber}" /> > </h:panelGroup> > But this works fine: > <h:inputText value="#{numberBean.myNumber}"> > <f:ajax render="test" /> > </h:inputText> > <h:panelGroup id="test"> > <script type="text/javascript"> > alert("running"); > </script> > <h:inputText value="#{numberBean.myNumber}" /> > </h:panelGroup> -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.