[ http://issues.apache.org/jira/browse/MYFACES-797?page=comments#action_12357139 ]
Simon Kitching commented on MYFACES-797: ---------------------------------------- Ok, I've tracked down the official spec for how <script> is handled: http://www.w3.org/TR/REC-html40/appendix/notes.html#notes-specifying-data The script and style tags need to be handled in a special manner, where the parser looks for the first occurrence of "</". I'll provide a patch to implement this. In the meantime, I believe you can work around this by using the standard script-hiding approach for browsers that don't handle scripting, because the ReducedHTMLParser is currently acting exactly like an old browser that doesn't recognise the special behaviour of <script>. <script ...> <!-- function messWithMyHead() { for (var i=0; i<tabList.length; i++ ) { } } // --> </script> I'll also try to figure out why an infinite loop occurs; even inserting the AddResource text at the wrong location would be better than that. Thanks for the report. See also: http://issues.apache.org/jira/browse/MYFACES-768 > t:inputCalendar + javscript(using variable tabList) = page hang. > ---------------------------------------------------------------- > > Key: MYFACES-797 > URL: http://issues.apache.org/jira/browse/MYFACES-797 > Project: MyFaces > Type: Bug > Components: Tomahawk > Versions: Nightly > Environment: jboss-4.0.2 > jdk1.5.0_04 > Firefox 1.0.7 > myfaces-20051107.zip > Struts 1.2.7 > Reporter: jeff porter > Attachments: ebusinees_Cal_JS_Prob.ear > > I started with the bug of t:calendar and onload not working in release 1.1.1 > I then moved on to the nightly release 20051107. > New bug... > If I have a page with <t:inputCalendar and > <script language="JavaScript1.3"> > function messWithMyHead() { > for (var i=0; i<tabList.length; i++ ) { > } > } > </script> > The page will never be displayed. > 1: I don't call the JavaScript, it just has to exist on the page. > 2: Method name is not the cause > 3: Remming out the for loop does not stop the problem > 4: REMOVING the for loop does allow the page to be displayed. > 5: REMOVING the <t:inputCalendar allows the page to be displayed. > 6: No error message is displayed in the JBoss console, it just hangs. > To prove this, download my ear (link at bottom) & go to the address... > > http://localhost:8080/ebusiness/ > (Change port if required) > The page will not be displayed. > Then go into the ear, then the war and open the file theTest.jsp > Removed the for loop lines (or the t:calendar), save & exit. > Go back to the address & the page will display. > Example ear of the problem at... > http://www.porter.eu.com/jeff/prob.ear (3meg - inc libs) > Hope someone else can verify this for me. > Jeff. :-) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
