[richfaces-issues] [JBoss JIRA] (RF-12548) rich:tabPanel does not work after ajax request
[
https://issues.jboss.org/browse/RF-12548?page=com.atlassian.jira.plugin.s...
]
Juraj Húska edited comment on RF-12548 at 11/20/12 12:58 PM:
-------------------------------------------------------------
User confirmed that the issue was not in RichFaces.
Marco, to your
[comment|https://issues.jboss.org/browse/RF-12548?focusedCommentId=1273447...],
please open another issue if you think that it can be another bug in 4.3.0.M2 or start
discussion at RichFaces forum.
was (Author: jhuska):
User confirmed that the issue was not in RichFaces.
Marco, please open another issue if you think that it can be another bug in 4.3.0.M2 or
start discussion at RichFaces forum.
rich:tabPanel does not work after ajax request
----------------------------------------------
Key: RF-12548
URL: https://issues.jboss.org/browse/RF-12548
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-panels-layout-themes
Affects Versions: 4.2.3.Final
Reporter: Marco Goetz
Assignee: Juraj Húska
I have a strange problem with the rich:tabPanel in combination with an ajax request and a
commandLink.
After clicking the a4j:commandLink "Update" Button the rich:tabPanel is not
switching anymore.
The browser's console log says:
{quote}
new RichFaces.ui.TabPanel("j_id_5:panel1", ({ajax:{incId:"1"},
activeItem:"j_id_9", isKeepHeight:false, cycledSwitching:false})) is not a
function
at jsf.js.jsf:3682
{quote}
Example Code:
{code}
<h:head>
</h:head>
<body>
<h:form>
<a4j:commandLink value="Update"
action="#{testBean.update}" render="contentDiv" />
<t:div id="contentDiv">
<rich:tabPanel switchType="client"
id="panel1">
<rich:tab>
Tab1
<h:commandLink
action="#{test.testAction}" />
</rich:tab>
<rich:tab>
Tab2
</rich:tab>
</rich:tabPanel>
</t:div>
</h:form>
</body>
{code}
The very strange thing is when I remove the the h:commandLink in Tab1 the switching works
fine after the ajax request.
When I change the render attribute to "@all" it works too, but that would be a
bad workaround.
I used MyFaces 2.1.8 and Richfaces 4.3.0.M1.
Problem stil exists with Richfaces 4.2.3.Final.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira