[JBoss JIRA] (RF-12765) Rich:tabPanel not possible to switch tabs when only dynamic tabs are present
by Tali Han (JIRA)
[ https://issues.jboss.org/browse/RF-12765?page=com.atlassian.jira.plugin.s... ]
Tali Han edited comment on RF-12765 at 2/21/13 6:02 PM:
--------------------------------------------------------
I looked into pom.xml it is using myfaces. I'll try to compile it with mojarra and let you knoe.
was (Author: talik):
1)I am using javax.faces-2.1.17.jar, that comes with distribution. I think it is Mojarra.
> Rich:tabPanel not possible to switch tabs when only dynamic tabs are present
> ----------------------------------------------------------------------------
>
> Key: RF-12765
> URL: https://issues.jboss.org/browse/RF-12765
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output
> Affects Versions: 4.3.0.M3, 4.3.0.CR2
> Environment: Linux, windows any browser Chrom, Mozilla
> Reporter: Tali Han
> Assignee: Brian Leathem
> Fix For: 4.3.1
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> Rih:Tab panel functionality is broken.
> If you have dynamically generated tabs, you'll be able to switch from first to last, and then to first, but you'll not be able to switch to any other tab again.
> Remove from example that comes with richfaces distribution first static tab for dynamic tabs and you'll be able to reproduce this behaviour.
> richfaces/tabPanel/samples/dynamic-sample.xhtml
> {code}
> <rich:tabPanel activeItem="#{dynamicPanelBean.activeTab}">
> <ui:remove>
> <rich:tab header="Static">
> <p>This tab is static one.</p>
>
> <p>All of the following tabs are dynamically generated using <b>a4j:repeat</b>.</p>
> </rich:tab>
> </ui:remove>
> <a4j:repeat value="#{skinBean.skins}" var="skinName">
>
> <rich:tab header="#{skinName}" name="#{skinName}">
> <f:facet name="header">#{skinName}</f:facet>
> <i> All the controls below are just standard JSF components skinned with RichFaces: </i>
> <hr />
> <h:form>
> {code}
--
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
12 years, 7 months
[JBoss JIRA] (RF-12765) Rich:tabPanel not possible to switch tabs when only dynamic tabs are present
by Tali Han (JIRA)
[ https://issues.jboss.org/browse/RF-12765?page=com.atlassian.jira.plugin.s... ]
Tali Han edited comment on RF-12765 at 2/21/13 6:02 PM:
--------------------------------------------------------
I looked into pom.xml it is using myfaces. I'll try to compile it with mojarra and let you know.
was (Author: talik):
I looked into pom.xml it is using myfaces. I'll try to compile it with mojarra and let you knoe.
> Rich:tabPanel not possible to switch tabs when only dynamic tabs are present
> ----------------------------------------------------------------------------
>
> Key: RF-12765
> URL: https://issues.jboss.org/browse/RF-12765
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output
> Affects Versions: 4.3.0.M3, 4.3.0.CR2
> Environment: Linux, windows any browser Chrom, Mozilla
> Reporter: Tali Han
> Assignee: Brian Leathem
> Fix For: 4.3.1
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> Rih:Tab panel functionality is broken.
> If you have dynamically generated tabs, you'll be able to switch from first to last, and then to first, but you'll not be able to switch to any other tab again.
> Remove from example that comes with richfaces distribution first static tab for dynamic tabs and you'll be able to reproduce this behaviour.
> richfaces/tabPanel/samples/dynamic-sample.xhtml
> {code}
> <rich:tabPanel activeItem="#{dynamicPanelBean.activeTab}">
> <ui:remove>
> <rich:tab header="Static">
> <p>This tab is static one.</p>
>
> <p>All of the following tabs are dynamically generated using <b>a4j:repeat</b>.</p>
> </rich:tab>
> </ui:remove>
> <a4j:repeat value="#{skinBean.skins}" var="skinName">
>
> <rich:tab header="#{skinName}" name="#{skinName}">
> <f:facet name="header">#{skinName}</f:facet>
> <i> All the controls below are just standard JSF components skinned with RichFaces: </i>
> <hr />
> <h:form>
> {code}
--
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
12 years, 7 months
[JBoss JIRA] (RF-12765) Rich:tabPanel not possible to switch tabs when only dynamic tabs are present
by Tali Han (JIRA)
[ https://issues.jboss.org/browse/RF-12765?page=com.atlassian.jira.plugin.s... ]
Tali Han commented on RF-12765:
-------------------------------
How else I can help?
> Rich:tabPanel not possible to switch tabs when only dynamic tabs are present
> ----------------------------------------------------------------------------
>
> Key: RF-12765
> URL: https://issues.jboss.org/browse/RF-12765
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output
> Affects Versions: 4.3.0.M3, 4.3.0.CR2
> Environment: Linux, windows any browser Chrom, Mozilla
> Reporter: Tali Han
> Assignee: Brian Leathem
> Fix For: 4.3.1
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> Rih:Tab panel functionality is broken.
> If you have dynamically generated tabs, you'll be able to switch from first to last, and then to first, but you'll not be able to switch to any other tab again.
> Remove from example that comes with richfaces distribution first static tab for dynamic tabs and you'll be able to reproduce this behaviour.
> richfaces/tabPanel/samples/dynamic-sample.xhtml
> {code}
> <rich:tabPanel activeItem="#{dynamicPanelBean.activeTab}">
> <ui:remove>
> <rich:tab header="Static">
> <p>This tab is static one.</p>
>
> <p>All of the following tabs are dynamically generated using <b>a4j:repeat</b>.</p>
> </rich:tab>
> </ui:remove>
> <a4j:repeat value="#{skinBean.skins}" var="skinName">
>
> <rich:tab header="#{skinName}" name="#{skinName}">
> <f:facet name="header">#{skinName}</f:facet>
> <i> All the controls below are just standard JSF components skinned with RichFaces: </i>
> <hr />
> <h:form>
> {code}
--
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
12 years, 7 months
[JBoss JIRA] (RF-12765) Rich:tabPanel not possible to switch tabs when only dynamic tabs are present
by Tali Han (JIRA)
[ https://issues.jboss.org/browse/RF-12765?page=com.atlassian.jira.plugin.s... ]
Tali Han commented on RF-12765:
-------------------------------
1)I am using javax.faces-2.1.17.jar, that comes with distribution. I think it is Mojarra.
> Rich:tabPanel not possible to switch tabs when only dynamic tabs are present
> ----------------------------------------------------------------------------
>
> Key: RF-12765
> URL: https://issues.jboss.org/browse/RF-12765
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output
> Affects Versions: 4.3.0.M3, 4.3.0.CR2
> Environment: Linux, windows any browser Chrom, Mozilla
> Reporter: Tali Han
> Assignee: Brian Leathem
> Fix For: 4.3.1
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> Rih:Tab panel functionality is broken.
> If you have dynamically generated tabs, you'll be able to switch from first to last, and then to first, but you'll not be able to switch to any other tab again.
> Remove from example that comes with richfaces distribution first static tab for dynamic tabs and you'll be able to reproduce this behaviour.
> richfaces/tabPanel/samples/dynamic-sample.xhtml
> {code}
> <rich:tabPanel activeItem="#{dynamicPanelBean.activeTab}">
> <ui:remove>
> <rich:tab header="Static">
> <p>This tab is static one.</p>
>
> <p>All of the following tabs are dynamically generated using <b>a4j:repeat</b>.</p>
> </rich:tab>
> </ui:remove>
> <a4j:repeat value="#{skinBean.skins}" var="skinName">
>
> <rich:tab header="#{skinName}" name="#{skinName}">
> <f:facet name="header">#{skinName}</f:facet>
> <i> All the controls below are just standard JSF components skinned with RichFaces: </i>
> <hr />
> <h:form>
> {code}
--
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
12 years, 7 months
[JBoss JIRA] (RF-12543) a4j:push after ajax-rendered does not have its javascript included
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-12543?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč commented on RF-12543:
---------------------------------
Official schedule and estimations are available in the [project Roadmap|https://issues.jboss.org/browse/RF#selectedTab=com.atlassian.jira...].
However please keep this discussion strictly technical.
---
I assume the push widget needs to be refactored that the Atmosphere won't actually never hang and connect again.
If you volunteer to help with this refactoring, we could include the fix sooner than later. I would be glad to help you.
> a4j:push after ajax-rendered does not have its javascript included
> ------------------------------------------------------------------
>
> Key: RF-12543
> URL: https://issues.jboss.org/browse/RF-12543
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Environment: RichFaces 4.2.2 FINAL
> Reporter: nimo stephan
> Fix For: 5-Tracking
>
>
> I have a4j:push within my page which should be rendered only if the property "pushIsActivated" is true. When changing the property by a button to true, then I want to make a ajax-rendering which renders the a4j:push. However, the javascript portion is not created within the aj4:push, hence the component does not work! I have to make a full page refresh, then the javascript portion is inserted and a4j:push works as expected. However, I have to do a full page refresh. I guess, it is a bug, because the a4j:push has a rendered-property which can be changed by ajax, hence it has to work after ajax-update.
> {code}
> <h:form id="my-form" prependId="false" style="display:none;">
> <a4j:push rendered="#{mybean.pushIsActivated}" address=".." onerror=".." ondataavailable="..">
> <a4j:ajax event="dataavailable" render="my-section"/>
> </a4j:push>
> </h:form>
> {code}
> If I only render my-form after changing the property, a4j:push does not work:
> {code}
> <h:form>
> <h:commandButton value="Activate Push " action="#{myBean.setActivatePushToTrue}">
> <f:ajax render=":my-form"/>
> </h:commandButton>
> </h:form>
> {code}
> I have to do a full page refresh, only then aj4:push works:
> {code}
> <h:form>
> <h:commandButton value="Activate Push " action="#{myBean.setPushActivateToTrue}" onclick="submit();" />
> </h:form>
> {code}
> Richfaces does insert the needed javascript only after a full page request:
> {code}
> <script type="text/javascript">RichFaces.Push.setPushResourceUrl.....;</script>
> {code}
> If I make a ajax-rendering, Richfaces does NOT (!) insert the needed javascript. Hence a4j:push does not work.
--
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
12 years, 7 months
[JBoss JIRA] (RF-12765) Rich:tabPanel not possible to switch tabs when only dynamic tabs are present
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12765?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-12765:
------------------------------------
[~talik] What implementation of JSF are you using? Mojarra? MyFaces? Also, what version?
If you are using MyFaces, please give it a shot with Mojarra and see if that fixes the issue. That will help us narrow down the problem.
> Rich:tabPanel not possible to switch tabs when only dynamic tabs are present
> ----------------------------------------------------------------------------
>
> Key: RF-12765
> URL: https://issues.jboss.org/browse/RF-12765
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output
> Affects Versions: 4.3.0.M3, 4.3.0.CR2
> Environment: Linux, windows any browser Chrom, Mozilla
> Reporter: Tali Han
> Assignee: Brian Leathem
> Fix For: 4.3.1
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> Rih:Tab panel functionality is broken.
> If you have dynamically generated tabs, you'll be able to switch from first to last, and then to first, but you'll not be able to switch to any other tab again.
> Remove from example that comes with richfaces distribution first static tab for dynamic tabs and you'll be able to reproduce this behaviour.
> richfaces/tabPanel/samples/dynamic-sample.xhtml
> {code}
> <rich:tabPanel activeItem="#{dynamicPanelBean.activeTab}">
> <ui:remove>
> <rich:tab header="Static">
> <p>This tab is static one.</p>
>
> <p>All of the following tabs are dynamically generated using <b>a4j:repeat</b>.</p>
> </rich:tab>
> </ui:remove>
> <a4j:repeat value="#{skinBean.skins}" var="skinName">
>
> <rich:tab header="#{skinName}" name="#{skinName}">
> <f:facet name="header">#{skinName}</f:facet>
> <i> All the controls below are just standard JSF components skinned with RichFaces: </i>
> <hr />
> <h:form>
> {code}
--
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
12 years, 7 months
[JBoss JIRA] (RF-12768) Metamer: rich:tabPanel: Tabs are not clickable and can't be removed in Firefox 18/19
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12768?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-12768:
------------------------------------
I committed an automated test demonstrating the failure in FireFox.
> Metamer: rich:tabPanel: Tabs are not clickable and can't be removed in Firefox 18/19
> ------------------------------------------------------------------------------------
>
> Key: RF-12768
> URL: https://issues.jboss.org/browse/RF-12768
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-output
> Affects Versions: 4.2.3.Final
> Environment: Ubuntu 12.04 LTS, JBoss AS 7.1, Firefox 18.0.1
> Reporter: Petr Mensik
> Assignee: Brian Leathem
> Fix For: 4.3.1
>
> Attachments: RF-12768.png
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> Adding new tabs to to rich:tabPanel works fine but you can't remove panels created this way and you also can't click on them so their content is never displayed.
--
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
12 years, 7 months
[JBoss JIRA] (RF-12682) extendedDataTable render issue with rich:tabPanel
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12682?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12682:
-------------------------------
Assignee: (was: Pavol Pitonak)
> extendedDataTable render issue with rich:tabPanel
> -------------------------------------------------
>
> Key: RF-12682
> URL: https://issues.jboss.org/browse/RF-12682
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.2.3.Final, 4.3.0.M3, 4.3.0.CR1
> Reporter: Kaveh A.
> Labels: extendedDataTable, render, richfaces, tabpanel
> Attachments: richfacesBug2.zip, RichFacesBugEclipseProject.zip
>
>
> This issue is not just specific to tabPanel. Anytime the extendedDataTable is hidden (when the page loads) and then it is made visible later the table can not display the data (table is empty at the load time).
> In this particular case if we load a page with two tabs. Furthermore if we have one extendedDataTable in each tab (the first tab shows and the second tab is not shown at first). In this case once the user clicks on the second tab and tries to populate the extendedDataTable (via any action). Then the table is not rendered properly. A sample project has been provided at the following link that further describe this issue. You can download the eclipse project attached at the end of the following message to reproduce this issue.
> https://community.jboss.org/message/783787
--
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
12 years, 7 months
[JBoss JIRA] (RF-12682) extendedDataTable render issue with rich:tabPanel
by Kaveh A. (JIRA)
[ https://issues.jboss.org/browse/RF-12682?page=com.atlassian.jira.plugin.s... ]
Kaveh A. commented on RF-12682:
-------------------------------
We have tried RichFaces 4.3.0.Final and this issue has not yet been resolved.
> extendedDataTable render issue with rich:tabPanel
> -------------------------------------------------
>
> Key: RF-12682
> URL: https://issues.jboss.org/browse/RF-12682
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.2.3.Final, 4.3.0.M3, 4.3.0.CR1
> Reporter: Kaveh A.
> Assignee: Pavol Pitonak
> Labels: extendedDataTable, render, richfaces, tabpanel
> Attachments: richfacesBug2.zip, RichFacesBugEclipseProject.zip
>
>
> This issue is not just specific to tabPanel. Anytime the extendedDataTable is hidden (when the page loads) and then it is made visible later the table can not display the data (table is empty at the load time).
> In this particular case if we load a page with two tabs. Furthermore if we have one extendedDataTable in each tab (the first tab shows and the second tab is not shown at first). In this case once the user clicks on the second tab and tries to populate the extendedDataTable (via any action). Then the table is not rendered properly. A sample project has been provided at the following link that further describe this issue. You can download the eclipse project attached at the end of the following message to reproduce this issue.
> https://community.jboss.org/message/783787
--
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
12 years, 7 months