From issues at jboss.org Thu Jan 2 20:41:32 2014 Content-Type: multipart/mixed; boundary="===============7794702389889415644==" MIME-Version: 1.0 From: Brian Leathem (JIRA) To: richfaces-issues at lists.jboss.org Subject: [richfaces-issues] [JBoss JIRA] (RF-13455) The rich:tabPanel no longer visits tab header facets while rendering a response. Date: Thu, 02 Jan 2014 20:41:32 -0500 Message-ID: In-Reply-To: JIRA.12528562.1388712642000@jira02.app.mwc.hst.phx2.redhat.com --===============7794702389889415644== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable [ https://issues.jboss.org/browse/RF-13455?page=3Dcom.atlassian.jira.p= lugin.system.issuetabpanels:all-tabpanel ] Brian Leathem updated RF-13455: ------------------------------- Issue Type: Bug (was: Feature Request) = > The rich:tabPanel no longer visits tab header facets while rendering a re= sponse. > -------------------------------------------------------------------------= ------- > > Key: RF-13455 > URL: https://issues.jboss.org/browse/RF-13455 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) = > Components: component-panels-layout-themes > Affects Versions: 4.3.4 > Environment: java 7, > tomcat 7, JBoss AS, = > mojarra, myfaces > chrome, firefox > Reporter: Alexey Shakov > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha3 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > I use ajax to update the header label of rich:tab. That is why label is p= laced in a header-facet. Since RF 4.3.4 this does not work: > {code:xml} > > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> > xmlns:c=3D"http://java.sun.com/jsp/jstl/core" xmlns:rich=3D"http://rich= faces.org/rich" xmlns:a4j=3D"http://richfaces.org/a4j" > xmlns:f=3D"http://java.sun.com/jsf/core" xml:lang=3D"en" lang=3D"en"> > > > > = > > > > > > > > > > > > > > > > {code} > testBean is a simple session-scoped HashMap. = -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrato= rs For more information on JIRA, see: http://www.atlassian.com/software/jira --===============7794702389889415644==--