[richfaces-issues] [JBoss JIRA] (RF-12545) Tab panel: attribute active item doesn't work correctly for disabled tabs

[Brian Leathem (JIRA)]

    [ https://issues.jboss.org/browse/RF-12545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12728496#comment-12728496 ] 

Brian Leathem commented on RF-12545:
------------------------------------

The linked pull request fails with dynamic panels, as it results in a nested call to setRowKey.  When the nested/inner rowkey evaluation completes, it erases the state of the outer rowkey.  We either need to find a way of achieving the same result without using the DataVisitor, or we need to stash the original reqest map value when setting up the rowkey, so that we can restore it when the rowkey is torn down.
                
> Tab panel: attribute active item doesn't work correctly for disabled tabs
> -------------------------------------------------------------------------
>
>                 Key: RF-12545
>                 URL: https://issues.jboss.org/browse/RF-12545
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: component-panels-layout-themes, regression
>    Affects Versions: 4.3.0.M2
>         Environment: RichFaces 4.3.0-SNAPSHOT
> Metamer 4.3.0-SNAPSHOT
> Mojarra 2.1.7
> JBoss AS 7.1.2.Final-redhat-1
> Java(TM) SE Runtime Environment 1.6.0_32-b05 @ Linux
> Chrome 22.0.1229.94 @ Linux x86_64
>            Reporter: Pavol Pitonak
>            Assignee: Lukáš Fryč
>             Fix For: 4.3.0.M2
>
>         Attachments: tabpanel.png
>
>
> # deploy Metamer and open http://localhost:8080/metamer/faces/components/richTabPanel/simple.xhtml
> # set activeItem=tab4
> # switch to tab3
> result:
> * when activeItem is set to tab4 (disabled one), an empty tab is rendered but nothing should be rendered
> * after switching to a non-disabled tab, it is rendered wrong (see attached screenshot)

--
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