From jira-events at lists.jboss.org Wed Jun 18 09:29:47 2008 Content-Type: multipart/mixed; boundary="===============6736003545129809940==" MIME-Version: 1.0 From: Mike Hanafey (JIRA) To: richfaces-issues at lists.jboss.org Subject: [richfaces-issues] [JBoss JIRA] Updated: (RF-3738) simpleTogglePanel ajax broken if filter is NONE -- body tag is missing Date: Wed, 18 Jun 2008 09:29:47 -0400 Message-ID: <29712809.1213795787658.JavaMail.jira@cloud.prod.atl2.jboss.com> In-Reply-To: 7588966.1213793917377.JavaMail.jira@cloud.prod.atl2.jboss.com --===============6736003545129809940== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable [ http://jira.jboss.com/jira/browse/RF-3738?page=3Dall ] Mike Hanafey updated RF-3738: ----------------------------- Attachment: tidy.txt AJAX log when filter is TIDY > simpleTogglePanel ajax broken if filter is NONE -- body tag is missing > ---------------------------------------------------------------------- > > Key: RF-3738 > URL: http://jira.jboss.com/jira/browse/RF-3738 > Project: RichFaces > Issue Type: Bug > Affects Versions: 3.2.1 > Environment: JDK 1.6, Facelets 1.14, JSF-RI 1.2_08 > Reporter: Mike Hanafey > Attachments: neko.txt, none.txt, tidy.txt > > > When: > > org.ajax4jsf.xmlparser.ORDER > NONE > > the following trivial page generates an AJAX response that does not have = a body element that encloses the actual body content (using 3.2.1.GA): > > > xmlns=3D"http://www.w3.org/1999/xhtml" > xmlns:ui=3D"http://java.sun.com/jsf/facelets" > xmlns:h=3D"http://java.sun.com/jsf/html" > xmlns:f=3D"http://java.sun.com/jsf/core" > xmlns:a4j=3D"http://richfaces.org/a4j" > xmlns:rich=3D"http://richfaces.org/rich"> > > > > immediate=3D"true" ajaxSingle=3D"true"> > > > > > > > > With Firefox 2, the XML parsing still works, but with Firefox 3 there is = an XML parsing error, so pages that actually are supposed to do something o= n the AJAX response appear to be dead. NOTE: In this trivial test case even= Firefox 3 does not generate the parsing error, but in the real example thi= s was derived from where the body content is more complex, then the parsing= error happens. But even in the trivial test case, the tag is missin= g. > I know the filter issue has come up many times before. It seems like a ve= ry good idea if the RichFaces developers would always run with the NONE set= ting so that these problems would be caught early. -- = This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: htt= p://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira =20 --===============6736003545129809940==--