July 2014 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13714) DropDownMenu not working inside tab-header

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-13714?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak updated RF-13714: ------------------------------- Attachment: tabPanel.png > DropDownMenu not working inside tab-header > ------------------------------------------ > > Key: RF-13714 > URL: https://issues.jboss.org/browse/RF-13714 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-menu > Affects Versions: 4.3.7 > Environment: Wildfly 8.1.0.GA => JSF 2.2 > Tested with recent Firefox and Chromium versions. > Reporter: Martin Höller > Assignee: Pavol Pitonak > Labels: dropDownMenu, tabPanel > Attachments: tabPanel.png > > > The <rich:dropDownMenu> component seems broken, when used in the header-fact of a <rich:tab>. The menu simply doesn't open. Here is simplified example-code to reproduce: > {code:xml} > <rich:tabPanel switchType="client"> > <rich:tab> > <f:facet name="header"> > <rich:dropDownMenu showEvent="mouseover" label="menu" mode="client"> > <rich:menuItem> > <a4j:commandLink value="menuItem" /> > </rich:menuItem> > </rich:dropDownMenu> > </f:facet> > </rich:tab> > </rich:tabPanel> > {code} > If I use the same menu-code in the <rich:tab> but outside the header-facet, it works. > This did work with Richfaces 3.3! -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-13708) Photoalbum: refresh over index page throws error

by Michal Petrov (JIRA)

[ https://issues.jboss.org/browse/RF-13708?page=com.atlassian.jira.plugin.s... ] Michal Petrov commented on RF-13708: ------------------------------------ The binding was created for RF-13492, I need access to the trees to reset their selection. I'll check if there is a way around it. > Photoalbum: refresh over index page throws error > ------------------------------------------------ > > Key: RF-13708 > URL: https://issues.jboss.org/browse/RF-13708 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: examples > Affects Versions: 4.3.6, 4.3.7, 4.3.8 > Environment: container: JBoss EAP 6.3.0.ER8, other EAPS as well > browsers: all > Reporter: Juraj Húska > Labels: photoalbum > Fix For: 4.5-Tracking > > > Refresh over index page of Photoalbum throws: > {code} > 14:31:05,563 SEVERE [javax.enterprise.resource.webcontainer.jsf.renderkit] (http-/127.0.0.1:8080-5) javax.faces.FacesException: Component ID overForm:PreDefinedTree:j_idt273 has already been found in the view. : javax.faces.FacesException: Component ID overForm:PreDefinedTree:j_idt273 has already been found in the view. > at com.sun.faces.context.ExceptionHandlerImpl.handle(ExceptionHandlerImpl.java:139) [jsf-impl-2.1.28.redhat-3.jar:2.1.28.redhat-3] > at com.sun.faces.lifecycle.Phase.doPhase(Phase.java:119) [jsf-impl-2.1.28.redhat-3.jar:2.1.28.redhat-3] > at com.sun.faces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:139) [jsf-impl-2.1.28.redhat-3.jar:2.1.28.redhat-3] > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:594) [jboss-jsf-api_2.1_spec-2.1.28.Final-redhat-1.jar:2.1.28.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:231) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.4.0.Final-redhat-17.jar:7.4.0.Final-redhat-17] > at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.4.0.Final-redhat-17.jar:7.4.0.Final-redhat-17] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.4.0.Final-redhat-17.jar:7.4.0.Final-redhat-17] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:344) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:926) [jbossweb-7.4.7.Final-redhat-1.jar:7.4.7.Final-redhat-1] > at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55] > {code} > After this error application cease to work. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-13687) TabPanel header is not updated after switching of tabs

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13687?page=com.atlassian.jira.plugin.s... ] Brian Leathem resolved RF-13687. -------------------------------- Labels: needs-qe (was: ) Resolution: Done Rewrote the client-side tab selection to require only a single rendering of the tab headers. This required explicitly triggering the tab@header meta component be rendered when the active tab is changed. @QE: this is a significant change for the tab/tabPanel components. Please be appropriately rigorous in your QA. > TabPanel header is not updated after switching of tabs > ------------------------------------------------------ > > Key: RF-13687 > URL: https://issues.jboss.org/browse/RF-13687 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.5.0.Alpha3, 5.0.0.Alpha3, 5.0.0.Alpha4 > Reporter: Juraj Húska > Assignee: Brian Leathem > Labels: needs-qe > Fix For: 4.5.0.Alpha3 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > If {{TabPanel}} header is updated dynamically with AJAX, then switching among the tabs shows not the updated value of the header, but the initial one. Its updated after refresh of the page. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-13687) TabPanel header is not updated after switching of tabs

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13687?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13687: ------------------------------------ Looking at the generated HTML: {code} ... <td id="form:j_idt41:header:inactive" class="rf-tab-hdr rf-tab-hdr-inact rf-tab-hdr-top" style="display: table-cell;"> 5 clicks </td> <td id="form:j_idt41:header:active" class="rf-tab-hdr rf-tab-hdr-act rf-tab-hdr-top" style="display: none;"> 0 clicks </td> <td id="form:j_idt41:header:disabled" class="rf-tab-hdr rf-tab-hdr-dis rf-tab-hdr-top" style="display : none"> 0 clicks </td> ... {code} One can see that the label attribute is rendered 3 times: once for each of the _active_, _inactive_, and _disabled_ tab headers. Only one of the rendered DOM nodes is getting updated with the new value. This is likely due to the repetition of the {{id}} attribute amongst the three rendered DOM nodes. This is incorrect HTML, and as such the behaviour is unspecified. Proper resolution of this issue will involve properly dealing with the active/inactive/disabled tab headers and rendering each tab header only a single time. > TabPanel header is not updated after switching of tabs > ------------------------------------------------------ > > Key: RF-13687 > URL: https://issues.jboss.org/browse/RF-13687 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.5.0.Alpha3, 5.0.0.Alpha3, 5.0.0.Alpha4 > Reporter: Juraj Húska > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > If {{TabPanel}} header is updated dynamically with AJAX, then switching among the tabs shows not the updated value of the header, but the initial one. Its updated after refresh of the page. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-13107) ajaxRenderer component are rendered even though they are in non-active switchable panel, causing JSF to fail to update DOM

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13107?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13107: ------------------------------- Summary: ajaxRenderer component are rendered even though they are in non-active switchable panel, causing JSF to fail to update DOM (was: ajaxRenderer component are renderer even though they are in non-active switchable panel, causing JSF to fail to update DOM) > ajaxRenderer component are rendered even though they are in non-active switchable panel, causing JSF to fail to update DOM > -------------------------------------------------------------------------------------------------------------------------- > > Key: RF-13107 > URL: https://issues.jboss.org/browse/RF-13107 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-validators > Affects Versions: 4.3.2 > Reporter: Jonáš Trantina > Assignee: Lukáš Fryč > Fix For: 4.3.4 > > Attachments: bug_reproducer.zip, reproducer_ajax.zip, rf13107ajax.png > > Original Estimate: 1 hour, 30 minutes > Remaining Estimate: 1 hour, 30 minutes > > We have a form with a tabPanel component with two tabs A and B. In A there is an input and its rich:message in B the same plus a button that submits and re-renders B. When B is opened (thus A is not rendered) and the form is submitted and validation fails, then no message is shown. > Note that: > 1) switchType must be set to server to ensure the A's rich:message is really not on the page. > 2) button in B must re-render only content of B > This is only a specific scenario, the issue might occur also in other situations (e.g. global messages tag outside of tabPanel is not rendered). > Please find the enclosed reproducer. > Snipper: > {code:xml} > <h:form> > <rich:tabPanel switchType="server"> > <rich:tab> > <h:inputText id="surname" value="#{richBean.surname}"> > <f:validateLength minimum="10"/> > </h:inputText> > <rich:message for="surname"/> > </rich:tab> > <rich:tab> > <h:panelGroup id="content"> > <h:inputText id="name" value="#{richBean.name}"> > <f:validateLength minimum="6"/> > </h:inputText> > <rich:message for="name"/> > </h:panelGroup> > <a4j:commandButton value="Submit" execute="content" render="content" /> > </rich:tab> > </rich:tabPanel> > </h:form> > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-13673) Backport the plain skin fix from RF 5

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13673?page=com.atlassian.jira.plugin.s... ] Brian Leathem resolved RF-13673. -------------------------------- Resolution: Done > Backport the plain skin fix from RF 5 > ------------------------------------- > > Key: RF-13673 > URL: https://issues.jboss.org/browse/RF-13673 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: skinning > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > Backport RF-11103. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-13682) Stateless view: CSS stylesheets not included in head after form submit

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13682?page=com.atlassian.jira.plugin.s... ] Brian Leathem reassigned RF-13682: ---------------------------------- Assignee: Brian Leathem > Stateless view: CSS stylesheets not included in head after form submit > ---------------------------------------------------------------------- > > Key: RF-13682 > URL: https://issues.jboss.org/browse/RF-13682 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.7 > Environment: OpenSuse 13.1 x64 > OpenJDK 1.7.0_51 > Apache Tomcat 8.0.8 > JSF: org.glassfish:javax.faces:2.1.28 > Reporter: Tony Cramer > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > Attachments: rf-demo-skinning.zip, rf-demo-skinning_and_style.zip > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > If view is stateless <f:view transient="true"... > Issue 1. skinning.css is not included after submitting a form at all. > Issue 2. Any other stylesheets manually included with h:outputStylesheet are not included in head but in body after submit. > Maven project reproducing the issue attached. > Please use "rf-demo-skinning_and_style.zip" - reproduces both issues. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-13687) TabPanel header is not updated after switching of tabs

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13687?page=com.atlassian.jira.plugin.s... ] Brian Leathem reassigned RF-13687: ---------------------------------- Assignee: Brian Leathem > TabPanel header is not updated after switching of tabs > ------------------------------------------------------ > > Key: RF-13687 > URL: https://issues.jboss.org/browse/RF-13687 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-output > Affects Versions: 4.5.0.Alpha3, 5.0.0.Alpha3, 5.0.0.Alpha4 > Reporter: Juraj Húska > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > If {{TabPanel}} header is updated dynamically with AJAX, then switching among the tabs shows not the updated value of the header, but the initial one. Its updated after refresh of the page. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-13585) Re-factor the components demo

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13585?page=com.atlassian.jira.plugin.s... ] Brian Leathem resolved RF-13585. -------------------------------- Resolution: Done I've fixed the reported issues. Yes, the components-demo samples _should_ all work. *However* it is not a priority at this time to run through them all and verify/resolve them. > Re-factor the components demo > ----------------------------- > > Key: RF-13585 > URL: https://issues.jboss.org/browse/RF-13585 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: examples > Affects Versions: 4.5.0.Alpha3 > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Re-factor the components demo to work with RichFaces 4.5 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 12 months

1
0
0 / 0

[JBoss JIRA] (RF-13585) Re-factor the components demo

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13585?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13585: ------------------------------------ I've removed the dependency management from the components-demo POM altogether as I believe it is redundant. A {{mvn clean verify}} build of the components-demo is successful after removing the dependency management. > Re-factor the components demo > ----------------------------- > > Key: RF-13585 > URL: https://issues.jboss.org/browse/RF-13585 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: examples > Affects Versions: 4.5.0.Alpha3 > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 4.5.0.Alpha3 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Re-factor the components demo to work with RichFaces 4.5 -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 12 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues July 2014